Exploratory testing with the Test & Feedback extension in Connected mode

Azure Test Plans | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015

To use the Test & Feedback extension in Connected mode you must connect to Azure DevOps or TFS 2015 and later. This automatically configures the extension based on your access level:

  • Users with Basic access can use the extension to perform exploratory testing, as described below.

  • Users with Stakeholder access can use the extension to respond to feedback requests or to provide feedback voluntarily. More details.

  • Users with Basic or Stakeholder access can use extension to respond to feedback requests sent by the team by choosing the Provide feedback link in the email. More details.


To use all the features described in this topic you must have either an Enterprise, Test Professional, or MSDN Platforms subscription; or have installed the Test Manager extension for Azure Test Plans available from Visual Studio Marketplace. See Manual testing permissions and access.


Connect to Azure DevOps or TFS

  1. If you want to use Azure DevOps, and you haven't already done so, sign up for a subscription now. Make sure you create a project when you create your subscription.

  2. If you haven't already, install the Test & Feedback extension.

  3. Open the extension in your web browser and select Connected mode.

    Start the extension in Connected mode

  4. Enter the Azure DevOps or TFS URL you want to connect to and choose Next.

    Enter the Azure DevOps or TFS URL you want to connect to

    If you are connecting for the first time, you may be prompted to sign in.

  5. After connecting to the server, the extension shows all the collections, projects and teams in that server. Select the project or team you want to connect to and choose Save.

    Select your project or team

    If there are many projects or teams, use the search textbox to find the one you need.

The extension is now ready to be used in Connected mode. Depending on your access level (Basic or Stakeholder) you will see the appropriate UI for either exploratory testing or providing feedback. The extension remembers your selection and remains connected until the session cookies expire or you explicitly disconnect from the server.

Create bugs or tasks

After you have connected, you are ready to begin testing your app.

  1. Start your exploratory testing session.

    Start your exploratory testing session

  2. Open the web application you want to test, and start exploring it.

  3. When you find an area that has a bug, take a screenshot of any part of the screen, make notes, or record your actions as a video.

    Take a screenshot, make notes, or record your actions as a video

    Some browsers may not provide all of the capture capabilities. See Which web browsers does the extension support?

  4. When you are done exploring and capturing information, create a bug or a task.

    Create a bug or a task from the captured information

  5. The bug or task form contains all your captured information. It also contains an image action log describing your interactions with the page (such as mouse clicks, keyboard typing events, touch gestures, and more) and page load data. Uncheck these options if you do not want to include this data in the bug or task.

    Decide whether to include the image action log and page load data

    The image action log is the sequence of steps you took that led to the issue. It can be used to reproduce the issue and understand the context. Page load data provides preliminary information about the time it takes to load the pages, such as the resource timings and navigation timelines.

  6. Enter a title for the bug or task and add any additional notes you require to the description. Then save the bug or task.

    Save the bug or task

    You can also add your findings to an existing similar bug.

  7. View a list of all your activities in reverse chronological order in the Session timeline page. It shows all the screenshots, videos, and notes you've captured, the work items such as bugs, tasks, and test cases you've already filed, and the work items you've explored.

    Review your captured information

    You can use the extension to explore work items in Azure DevOps or TFS.

  8. To view a bug or task in Azure DevOps or TFS, choose the link in the session timeline.

    View a bug or task

    This opens the work item form in Azure DevOps or TFS.

    The bug or task in TS or TFS

How do I play the video recordings I created with the extension?

Create test cases

The extension lets you create test cases as you explore your application.

  1. When you find a scenario where you want to create a test case, choose Create test case.

    Creating a test case

  2. The test case form contains a list of all your actions up to this point while exploring the app (it reads them from the image action log).

    The actions for the new test case

  3. Enter a title for the test case and then edit it as required. For example, uncheck the action steps you don't want to include in the test case, edit the captured text, and add the expected result. Then save the test case.

    Editing new test case

  4. Continue exploring the application. Create more bugs, tasks, or test cases as required.

End your testing session

  1. When you're done, stop your session.

    Stop the exploratory testing session

  2. If you are using Azure DevOps, or TFS 2017 and higher, open the Session timeline page and choose the "view" icon to see your completed exploratory sessions in Azure DevOps or TFS.

    View the exploratory testing session

    Alternatively, open the Recent exploratory sessions list directly in the Runs page of Azure Test Plans or the Test hub in TFS (see Web portal navigation).

    View exploratory testing sessions on the server

See your exploratory session results

After you file bugs, create tasks, or create test cases, all these show up in the "Recent exploratory sessions" page in Azure Test Plans or TFS.

How do I play the video recordings I created with the extension?