QMetry for Jira (QTM4J) - Exploratory Testing is a Chrome Extension that has been designed to empower users to carry out testing while they explore websites, to ensure that testers’ time is invested in investigating the site instead of writing every single test activity, and to cultivate the culture of flawless communication in the organization.
QMetry Exploratory Testing helps users identify problems with the website/application under test. The Chrome Extension verifies the website through a browser to confirm that it is functioning properly.
The functionality traces actions performed during Exploratory UI testing in browser and convert it into modular code that can be used for automated regression Tests.
Each event and navigation are recorded, which provides ready-to-use Automated Documentation.
The tool allows its users to log defects just with a mouse click. It enables users to add visuals while logging defects, which makes it easy for the development team to catch the scenario where the application fails.
All the features intend to generate precise and clear communication, which lessens the chances of confusion and enhances the productivity of resources.
Install QMetry for Jira (QTM4J) - Exploratory Testing Chrome Extension and get started recording the events you perform on applications/websites. View results of these recorded sessions on QMetry for Jira (QTM4J) - Exploratory Testing instance.
If QMetry permissions are enabled:
Test Case View, Create, Edit, Versioning, Manage Folder.
Exploratory Testing View and Modify permissions.
Steps to initiate Exploratory Testing using QMetry for Jira (QTM4J) - Exploratory Testing
Users can record test sessions using QMetry for Jira (QTM4J) - Exploratory Testing Chrome Extension. These sessions will be recorded and stored in QMetry Test Management for Jira instance that you mentioned while logging into the Chrome Extension.
Record while you Explore
Once you log into QMetry for Jira (QTM4J) - Exploratory Testing, the next window opens asking for details on the test session.
Project: Select the Jira Project in which session to be created.
Name: Enter the session name by which the test session will be identified.
Environment: Mention the Platform against which the is to be executed. By default, it will show the currently using OS and browser.
Tags: You can tag the session to categorize it. You can create multiple tags for a session.
Notes: Enter required notes or comments here in the text box.
Click on the Start Recording button to initiate the recording of your actions on the website or application.
Note: It is recommended that you open the site you want to explore before you start recording.
The icon beside the address bar indicates that the recording is now in-progress.
You can add Bugs/Defects, Audio and Annotations to your current recording.
There are two main buttons.
Save Recording: Once you are done recording the session click on the Save Recording button to upload the session to QMetry for Jira.
Cancel Recording: If you want to cancel the session recording, click on the Cancel Recording button. If a bug is logged before canceling the recording, it will be added to Jira same as Logging Bug without Session.
You can add a voice-over to the recording by clicking on the icon.
The icon starts displaying beside the address bar.
When you want to stop audio recording, click on the icon at the right of the address bar.
It displays the stopwatch. Click on the Stop button to stop the audio recording.
To cancel the audio recording, click on the Discard button.
How to play the audio recording?
Open the test session to which the audio recording was attached.
Open the Document tab.
You can see the Audio Recordings on the screen.
Play the recorded audio.
Users can use Assertion to get confirmation on the existence of particular components on the website, for example, a particular button, text, etc.
During the ongoing recording session, if you find some important components on the website that you can not avoid, then click on the Start Assertion button.
Once you are done clicking on that element or selecting the text for assertion and then click on the Stop Assertion button to stop its functionality.
When you view the recorded sessions, the Assertions will be displayed as Expected Result as below.
On the QMetry for Jira (QTM4J) - Exploratory Testing Extension -
Text Notes: Annotations can be added while recording the test session. Enter annotation and click on the Add Text Notes button.
Pause: Click on the icon to pause the session recording for the time being. You can resume the recording at your convenience.
Play: Click on the Play icon to resume the test recording from where it was paused.
You can log defect to the session while recording the test session. The defect gets logged into Jira.
Note: Logging defect operation will pause your session for a while. If you wish to resume the session, then close the Log Defect screen after logging the bug.
Click on the Bug icon
The screenshot of the current page opens in a separate tab.
The page also have options like any other image editor.
Users need to fill all required values to log a bug. Following are the values that the user can log a defect with :
Project : Select the project for which the issue is to be logged.
Issue Type : Select the issue type from Story, Task, Bug. The Issue Types populate according to the Issue Types enabled under QMetry Project Settings.
Summary : Enter the Summary that represents a brief about the issue.
Description: Describe the issue in detail in this text area.
Priority : Select the priority of the issue from the drop-down list.
Assignee: Select the assignee who will work on the issue from the drop-down list.
Versions: Select Affected Version applicable to the Defect.
Components : Select the Component applicable to the Defect.
Labels: Select the Labels applicable to the defect. You can select multiple options for the field.
You can see the count of defects logged for the session/test once the session is completed.
On clicking on the defect count in the grid will show the defect in the Defect tab.
To view the issue details in Jira, click on the Key. It opens the Jira details page in a separate tab.
In the Jira issue page, the Environment details are displayed for the bug which is added through exploratory testing.
If you do not see the Environment Details section on the page, then first enable it from more options as shown below.
Log Defects without Sessions
You may come across certain defects that you can not associate with a session instantly. QMetry for Jira (QTM4J) - Exploratory Testing allows you to log defects even without recording a session.
Defects, logged without session, are added as bugs in QMetry Test Management for Jira.
1. Open the QMetry for Jira (QTM4J) - Exploratory Testing Chrome Extension.
2. Click on the Log Defect button at top right corner of the QMetry for Jira (QTM4J) - Exploratory Testing extension main screen.
3. It captures the screenshot of the website screen currently open.
4. Enter defect details the same as you do when logging a defect during the session.
5. Click on the Log Defect button.
A defect will be added directly to the selected project in Jira.
View and Manage Recorded Sessions
Users can view the recorded sessions in QMetry Test Management for Jira by following the below steps.
Log into Jira.
Go to QMetry menu > Exploratory Testing.
The screen displays a list of recorded sessions. Users can View, Manage and Create Test Cases from the recorded sessions.
The records display the following details about the session :
Name: Name of the session.
Environment: Environment on which it has been tested.
Tags: Tags mentioned while creating session.
Status: Status of the session. It shows "In Progress" when the session is being created, shows "Completed" once the session is finished and uploaded to QMetry.
Events: The count of Events recorded.
Defects: Count of defects logged during the session.
Recorded By: Username of the user who created a session.
Recorded On: Date and time when the session was recorded.
Filter Session Records
If it is a long list of recorded sessions, then you can apply a filter to get the required session.
The following filters can be applied to search required sessions:
Session Name: Search session by its name.
Tags: Search test session by Tags attached to it.
Platform: Search test session by Platform that was mentioned while its creation.
Status: Search test session by its status either "In Progress" or "Completed" or "All"
Created On: Mention the date range within which the test session was created.
Created By: Select user(s) to view sessions created by them.
Once you get the required sessions on the screen, just click on the session you want to view the recordings of.
The next screen shows the following tabs on it:
Screens : The tab shows all the screens captured during the Session. Read more in the section described below.
Document : The tab shows the steps along with screenshots. Read more in the section described below.
Event Detail : The tab shows events performed to record a session. For example, Click, Type, etc. Read more in the section described below.
Defects : The tab shows a list of Defects added to the session while recording it. Read more in the section described below.
Edit Session Details
Open the session detail page that you want to edit.
The values of Name and Platform are editable. Click on the respective field values. Make required changes in the details.
Users can delete test sessions that are no more required.
Go to QMetry menu > Exploratory Testing. The screen displays recorded sessions.
Click on the delete icon of the session you want to delete.
On the session details page, open the Screens tab. It contains screens captured during testing activity. The thumbnails are displayed on the sidebar at the left.
Click on the thumbnail to view the full image at the right.
A. Click on the download icon to download the image.
B. Click on the icon to view the image on the full screen.
The maximized image on the full screen:
Each and every event on the website are recorded in the form of test steps.
The Document tab displays Screenshot thumbnails with its Step Details, Input Data and Expected Output. The recording creates automated documentation that you can read and interpret easily.
Step Details is the action you perform, Input Data is the website you are exploring and Expected Output is an Assertion that you supplied while recording the session.
All the things are captured in the form of text and described as documentation.
Step Details, Input Data and Expected Output fields are editable. You can modify the field values as per requirement. The search box is provided at the top to search the required details by its Summary/Test Data/Expected Result.
The Event Detail tab displays event details of each event carried out during recording the session.
There are three vertical panels adjacent to each other:
The first panel displays events in sequence.
Second panel displays an image for the selected event.
The third panel displays the Properties and Values of the selected event.
The Defects tab displays bugs that you logged while recording the session. This issue is created as "Bug" in QMetry Test Management for Jira.
On the session detail page, open the Defects tab.
To open the issue detail page, click on the Key.
Create Test Case from Recorded Session
Users can create test cases in QMetry from the sessions recorded during exploratory testing. It saves time as users get automated test cases without writing them manually.
Go to QMetry menu > Exploratory Testing.
Open the session you want to create a test case from.
To create a test case directly from the recorded Exploratory Testing session, click on the Create Test Case button at the top right corner.
The Create Test Case screen opens.
You can add/edit the required details for the test case. If a custom field is marked as mandatory in Configuration, users can enter values for such mandatory fields here and proceed towards test case creation.
A test case is created in the Test Case tab under Test Management (QMetry menu > Test Management).
The Session Name is populated as Summary.
Events are populated as Test Steps.
Images captured during the session are available as attachments with corresponding test steps.