- 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 converts 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 on a mouse click. It enables users to add visuals while logging defects, which makes it easy for 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 Exploratory Testing Chrome Extension and get started recording the events you perform on applications/websites. View results of these recorded sessions on QMetry Exploratory Testing instance.
Steps to initiate Exploratory Testing using QMetry Exploratory Testing
Step 1. Install QMetry Exploratory Testing chrome extension.
Step 2. Username and Password of QMetry Test Management for Jira.
Step 3. Start exploratory testing and recording sessions through QMetry Exploratory Testing.
How to install QMetry Exploratory Testing Chrome Extension
(A) If you are using the Exploratory Testing module very first time, then go to QMetry menu > Utility > Exploratory Testing.
Click on the Download Chrome Extension link at top right corner.
(B) As an alternate, click on the link below to open QMetry Exploratory Testing page in Chrome web store.
Once the extension is added to your chrome browser, it will appear like below.
Log into QMetry Exploratory Testing Extension
Open the Chrome browser.
Click on the QMetry Exploratory Testing icon at right as shown above.
If you are using QMetry Exploratory Testing Chrome Extension for the first time, then provide
- Product: Select QMetry for JIRA -Test Management. Refer to the table below in this section for more details.
- Jira Add-on Type: Select the type Cloud/On-premise as applicable.
- Jira URL: This is your QMetry Test Management for Jira instance.
- Username and Password of QMetry Test Management for Jira.
Click on the Login button.
Product Selection on Chrome Extension
If you’re using –
Product to select from Chrome extension
QMetry for Jira - Test Management Add-on
QMetry for Jira - Test Management
Exploratory Testing in QMetry for Jira - Test Management Server Add-on
QMetry for Jira - Test Management
Exploratory Testing (Record)
Users can record test sessions using QMetry 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 Exploratory Testing, the next window opens asking for details on the test session/test scenario.
- Name: Enter the session name by which the test session/test scenario will be identified.
- Platform: Mention the Platform against which the test scenario is to be executed.
- Tags:You can tag the session to categorize it. You can create multiple tags for a session e.g., Import, Export, Integration.
- Extra 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.
You can add a voice-over to the recording by clicking on the
The icon is started displaying beside the address bar.
When you are done with audio recording, click on the icon at the right of the address bar.
It displays the stopwatch. Click on the Stop button to stop audio recording.
To cancel the audio recording, click on the Discard button.
How to play the audio recording?
- Open the test scenario/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. You can also download the recordings.
User can use Assertion to get confirmation on existence of particular components on the website, for example, a particular button, text, etc.
During the on-going recording session, if you find some important components on the website that you can not avoid, then click on the Start Assertion button. It will enable the as
Once you are done clicking on that element or selecting the text for assertion, and then click on the Assertion button again to stop its functionality.
When you view the recorded sessions, all the Assertions will be displayed as below.
On the QMetry Exploratory Testing Extension -
- Annotations: Annotations can be added while recording the test session. Enter annotation and click Add.
- 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.
- Stop: Click on the icon to stop the session recording. The uploading will start on stopping the session recording.
You can log defect to the scenario 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 current page opens in a separate tab.
- The page also have options like any other image editor.
Annotating Screenshot: You can annotate the screenshot you captured using the features available on the editor. It allows to describe any bug or defect more precisely, which ultimately makes it more comprehensive.
Custom fields (UDFs) are now supported while logging bugs from the Exploratory Testing screen. Testers can avoid any obstacles in logging bugs due to mandatory custom fields.
Along with the following system fields, users can now log bugs with custom fields.
- Project: Select the project for which the defect is to be logged.
- Issue Type: Select the issue type from Bug, Enhancement, New Feature.
- Summary: Enter the Summary that represents brief about the defect.
- Description: Describe the defect 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.
- Labels: Select the Labels applicable to the defect. You can select multiple options for the field.
- Custom Fields: All mandatory as well as optional fields will be displayed e.g., Testing Type, Testing Estimation.
You can see the count of defects logged for the tests.
On clicking on the defect count in the grid opens the Defect screenshot attached in support of the defect.
You can view the details related to the defect.
Log Defects without Sessions
You may come across certain defects that you can not associate with a session instantly. QMetry 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.
Open the QMetry Exploratory Testing Chrome Extension.
Click on the Log Defect button at top right corner of the QMetry Exploratory Testing extension main screen.
It captures the screenshot of the website screen currently open.
Enter defect details same as you do when logging a defect during the session.
Click on the Log Defect button.
A defect is added to the Issue module in the corresponding project.
After performing testing task through QMetry Exploratory Testing, users can then view the recorded sessions in QMetry Test Management for Jira.
- Log into QMetry Test Management for Jira.
- Go to QMetry menu > Utility > 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 Session Name, the Platform on which it has been tested, Status, and the Date and Time it has been Recorded On. The count of Events recorded and Defects logged for the session are also displayed on the screen.
Filter Session Records
If it is a long list of recorded sessions, then you can apply filter to get the required session.
The following filters can be applied to search required sessions:
- Session Name
- Tags: Search test scenario by Tags attached to it.
- Platform: Search test scenario by Platform that was mentioned while its creation.
- Status: Search test scenario by its status either "In Progress" or "Completed" or "All"
- Recorded Duration: Mention the date range within which the test scenario was created.
Just click on the session you want to view the recordings of.
The next screen shows the following tabs on it:
- Event Detail
Users can delete test sessions that are no more required.
Go to QMetry menu > Utility > Exploratory Testing.
View the recorded sessions.
- Select session that you want to delete by checking the check box(es). Multiple sessions can also be selected at a time.
- Click on the Bulk Remove button at right to delete the session(s) selected on the grid.
Edit Session Details
Expand the upper panel by clicking on More Details at top right.
It opens session details fields in editable mode. Hover the mouse over fields and the pencil icon appears for fields which are editable.
Session Name, Note and Tag are editable. Make required changes in the session details.
On the session details page, open the Screens tab. It contains screens captured during testing activity. The thumbnails are displayed on the sidebar at left.
Click on the thumbnail to view the full image at right.
Your each and every event on the website are recorded in the form of test steps.
The Document tab displays Screen Shot 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 your 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 Event Detail tab displays event details of each event carried out during recording the session.
There are three vertical panels adjacent to each other:
- First panel displays events in sequence.
- Second panel displays image for the even selected in the first panel.
- Third panel displays Property and Value for the event selected in the first panel.
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 Entity Key that opens the issue in the Issue module.
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 > Utility > Exploratory Testing.
Open the session you want to create test case from.
You can see the Create Test Case option at top right corner.
It opens Create Test Case screen with QMetry for Jira fields on it.
Fill required details and click Create.
An issue is created in Jira.
Open the issue detail page.
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.