In most cases separate from the Acceptance Criteria noted to a task, User Story or Feature, you as a tester should try and find issues that relate to the functionality but were not covered or thought of before. This is what we call exploratory testing. Exploratory testing is not just randomly clicking around (monkey testing), but is beforehand thinking what scenario's could result in unexpected behaviour of the application. See below for a list of examples of exploratory testing.

• Quality engineers (QA)

• Check out the browser testing page in Wiki.

DevOps has a feature where you as tester can record actions via a browser extension and automatically connect the executed steps to a task.

Extension: Test & Feedback To install the extension follow this link

Connect the extension to DevOps board

1. Go to settings by clicking on the settings icon (see below)
2. Add the server URL of the project in DevOps
3. Select the team you are going to do work for *you can always switch teams or projects if needed

Start tests

1. Press the Play button
2. Now you can use the loop icon to add your actions to a DevOps Task

Log/Store your work When done you can store the steps taken to a task. You can create either a task, a bug or even a test case The created task will automatically be added as a child of the workitem to which you chose to commit the exploratory testing

Other functionality There are other options such as recoding a video or adding notes. Explore!

The tool can also be used to record user/browser actions. The recording is saved as a .webm file. The recording can be downloaded and added as an attachment to the bug/task. Playing the recording you will need to install VLC player. (*you can request for an install of VLC via the RBI Software Portal)