Page History

...

1. Import tasks and from the Team Server (posted by the nightly server execution) as described in Importing Results into the UI.
2. Address any quality tasks assigned to you:
   1. Review the assigned tasks in the Quality Tasks view as described in Reviewing Results and the testing product user’s guide.
   2. If needed, reassign tasks as described in Reassigning Tasks to Other Team Members.
   3. Address the remaining issues (e.g., by correcting code, updating the test suite, performing a code review, etc.). See the testing product’s user’s guide for details.
3. Work on the assigned implementation tasks.
4. When creating new code or working on existing code:
   1. Test new and modified code according to the team’s designated policy. You can do this by starting Quick Mode analysis interactively, or letting it run in continuous mode. 
   2. Fix the problems reported in the Quality Tasks view. See the testing product’s user’s guide for details on resolving specific types of tasks
   3. Use the Rerun failed tests or Rereun tests button (in the Test Progress view) to check if your changes resolved the reported quality tasks.
      
      
      
      
      
      
5. Add any new or modified source code and testing assets to source control so that they can be integrated into the regression test suite.

...

1. Import tasks and from the Team Server (posted by the nightly server execution) as described in in Importing Results into the UI.
2. Address any quality tasks assigned to you:
   1. Review the assigned tasks in the Quality Tasks view as described in Reviewing Results and the testing product user’s guide.
   2. If needed, reassign tasks as described in Reassigning Tasks to Other Team Members.
   3. Address the remaining issues (e.g., by updating the test suite, reporting the problem to development, capturing a JUnit test case that helps development reproduce the problem, etc.). See the testing product’s user’s guide for details.
3. Work on the assigned testing tasks.
4. Create new tests according to the team’s designated policy. See the testing product’s user’s guide for details.
5. Address issues found (by reporting the problem to development, capturing a JUnit test case that helps development reproduce the problem, etc.). See the testing product’s user’s guide for details.
6. Add any new or modified testing assets (e.g., .tst files) to source control so that they can be integrated into the regression test suite.

...