QMetry configuration

learn how to configure for the integration of qualys container to broaden the observability of your hybrid it estate the setup for with qmetry, requires several procedures, most of which are in , but the initial procedure requires access to the qmetry console further, the following prerequisites are required qmetry account the administrator should have an active qmetry account on the specific qmetry instance user want to connect to if user don't have one, user need to sign up for a qmetry account access to a qmetry instance ensure that user have access to the specific qmetry instance where the projects, test suites and test cases are hosted users need the url or web address of the qmetry instance user want to connect to project membership users must be part of the qmetry projects user intend to access ensure that users have the necessary project membership to retrieve information about projects, test suites and test cases access policy as platform administrator and administrator ensure that the user has the necessary access policies the user should have the platform administrator role to create and manage connections effectively the user needs the administrator role, which allows them to create and manage configurations review and execute the content in the following sections in the order they are presented create a qmetry api token in order to establish a connection, the first configuration procedure, you must first acquire a qmetry api token, which is available only from the qmetry console use the following procedure navigate to the sub menu "open api" from the "integrations" menu on the left hand side of the page qmetry will automatically generate an api token click the copy api key icon to copy the existing key create a connection to qmetry establishing a connection to qmetry is prerequisite to configuring the service use the following procedure click on settings → service iam → connections → add new → add connection choose platfrom from the connection type dropdown list select qmetry provide a local account name for reference add the host qmetry api url of the qmetry host (e g , https //testmanagement qmetry com/ ) paste the api key created in the previous section, create a qmetry api token devops configuration for qmetry, recent customers note this procedure is valid only for customers onboarded 6 june, 2024 or after having established a connection, you must complete the configuration procedure take note of the following caveats qmetry tool can only be configured at the project level multiple test suites can be selected against projects test suites are just a way to restrict what all data user needs for a given project qmetry will only sync data available with connection configured against it at the project level, technical services are always configured as mutually exclusive if two users having same privileges tries to onboard the technical service for the same project only the first user can create the technical service it will not be listed for the second user to onboard use the following procedure to complete the configuration navigate to → settings & utilities → application configurations select an existing application or create a new application navigate to "add tools" step select the phase as test click add tool configuration from tool engine , select qmetry map your execution status to four levels passed, failed, skipped and blocked select the respective statuses into the respective categories click add configuration editing configuration use the following procedure to edit the configuration click on overflow menu and select "edit" option to edit the tool modify the execution status click save configuration deleting configuration use the following procedure to delete the current configuration click on overflow menu and select "delete" option to delete the tool click delete on the confirmation modal to proceed to delete onboarding the qmetry technical service after configuring devops for qmetry, you must onboard it as a technical service note the following caveats qmetry tool can only be configured at project level multiple test suites can be selected against projects test suites are just way to restrict what all data user needs for a given project it will only sync data available with connection configured against it at project level, technical services are always configured as mutually exclusive if two users having same privileges tries to onboard technical service for the same project only the first user is allowed to create the technical service, as the project is already on boarded, it will not be listed for the second user to onboard use the following procedure navigate to > settings & utilities > application configurations click on overflow menu for the chosen application and click onboard technical service note displays all the phases for which the tool has been configured for the application select the phase as test select the tool engine as qmetry connection select connection name from the dropdown menu deleting the qmetry technical service the administrator may, at will, delete the qmetry technical service use the following procedure navigate to → settings & utilities → application configurations expand the application to see all the associated phases click the overflow menu associated with the test phase click delete technical service reviewing test suite data in di after has been fully configured, displays all test suites being tracked by qmetry in the table view at the bottom of the test page the view provides general information about each test suite such as status (how many tests were skipped, passed, failed and blocked), total number of tests in the suite and the execution date detailed information about each suite are available by clicking the overflow menu for that test suite and selecting view details responds by navigating to the details page for that suite, where additional information regarding activity and history is available the activity tab presents a graphic presentation of the tabular data on the table the historical details tab presents additional details such as code smells and bugs on both tabs you have the option of selecting a time frame for testing from the duration control located in the upper right