Ensuring a robust testing process is crucial for successful development. Key practices like incorporating Acceptance Criteria in User Stories and leveraging Acceptance Tests for validation are essential. These practices contribute to efficient testing workflows. They not only enhance the QA (Quality Assurance) process but also ensure the delivery of high-quality software with Agile teams.
If you still need help, visit SSW Consulting Services and book in a consultant.
User Acceptance Testing (UAT) is common in software release cycles, but it can often be treated as a secondary backlog of work that's managed independently of the development Sprint. This separation adds friction, creates delays, and costs more money for every feature. UAT is incredibly valuable, so make sure you're doing it right.
Acceptance Criteria (from the Product Owner) help to answer the question "How will I know when I'm done with this Product Backlog Item (PBI)?". It defines the exact requirements that must be met for the PBI to be completed. It is the Product Owner's responsibility to ensure that all Acceptance Criteria has been added - otherwise they should not expect that work to be done.
When you use Microsoft Azure Test Plans to create test plans and test suites for your project, there are several approaches that you can take.
You can create a test case in Azure Test Plans directly from a Work Item (e.g. a Product Backlog Item or Bug) and also from a Test Plan or Test Suite.
In Azure Test Plans, you can assign test cases for different configurations to be run by different testers.
In Azure Test Plans, each test case has configurations defined against it and these can be used to define which environments to use for a test.
Developers sometimes think they're done when they finish coding and check in.
It's easy to forget about testing, but this will often result in rework or bug fixes for the developers - in other words, more work!
Keeping an eye on the results of acceptance testing can help you understand where things are really at in the Sprint.
Acceptance Tests check that the Acceptance Criteria on a User Story are met.
Test cases that define these acceptance tests should be written during story development and managed in the same system as the code (e.g. Azure DevOps). This allows for easier traceability between the code and the tests related to that code.
A combination of human and automated tests is likely to be required to complete the acceptance tests for a User Story.
Use Microsoft's Test & Feedback extension to perform exploratory tests on web apps directly from the browser.
Capture screenshots (and even videos), annotate them and submit bugs into Azure DevOps as you explore your web app - all directly from the Chrome browser (Edge and Firefox are also supported).
Test on any platform (Windows, Mac or Linux) on different devices - without the need for pre-defined test cases or test steps.
Organize your Test Cases by adding them to a Test Plan or Test Suite. One Test Plan per Sprint is recommended.
A Test Plan consists of a number of Test Suites and/or Test Cases.
- Do you include UAT in each Sprint?
- Do you include Acceptance Criteria in your PBIs?
- Do you create one test plan per Sprint?
- Do you know how to create a Test Case with Azure Test Plans?
- Do you know how to assign a tester to test configurations?
- Do you know how to configure which environments to use for a particular test?
- Do you know how to check the status and statistics of the current Sprint?
- Do you write Acceptance Tests to verify Acceptance Criteria?
- Do you do exploratory testing?
- Do you know how to add a Test Case to a Test Plan in Azure Test Plans?
- Do you know how to record your screen?
- Do you follow BDD?
- Do you do automated UI testing?
- Do you understand why testing is important?