Page History
Info |
---|
By adopting a methodology like SCRUM, you will divide work into small iterations (sprints) and your team will work together towards a defined goal (sprint goal). Collaboration is at the core of the team and having the visibility of work is essential to high-performance. Testing should occur throughout the whole sprint and is as it takes part of the definition of done, so no user story is completed without having passed the tests. By this reasonThis way, the whole team should have has the visibility of tests and its their progress. |
Tip |
---|
If you are part of a SCRUM based Team we recommend at leastyou to:
Bellow we will detail Here are the steps that you can follow.: |
UI Steps | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
In short, after successful installation & setup, we advise you to:
- create a Test Plan(s) per sprint
- configure your existing Agile Boards (i.e. Scrum Board of active sprint) to show Test Plans and (Sub) Test Executions assigned to your Sprints and to show the coverage status on the covered issues
...
- Overall Coverage Report, for evaluating the current coverage status of the coverable entities (e.g. user stories)
- Traceability Report, to quickly filter out relevant entities based on their coverage, check the runs of related Tests and reported defects
- Test Executions Report and/or Test Plans Report, as a means to see the results obtained on different environments, on different revisions of the SUT, and to check the reported defects if they're still to be resolved or not
...
|