Different ways to manage code review activities in SpiraTest?

Tuesday, February 8, 2011

I manage the development and validation activities of a set of statistical programs in a Spiratest project, and I have to perform a quality review for each of the programs.

What I actually do is creating a requirement for each program in my Spiratest project, with a same description (the list of points to verify during the code review), and then a test case from each requirement, with same test steps (the list of points to verify during the code review).

Do you think that it's the best way to perform code review activities using Spiratest? Would you have some advices to avoid creating a requirement for each of the program?
1 Replies
Tuesday, February 8, 2011
re: JulienVan Tuesday, February 8, 2011

If you are running SpiraTest v3.0 or greater you could use the Comments feature to add comments to the requirement. So what you could do is add a custom list property to store the review status of the Requirement (Draft, Reviewed, Updated, etc.). Then when you do the actual review you could add the review notes as comments, then change the status.

Also if you upgrade to our SpiraTeam product, it has an additional artifact called a Task that is assigned to requirements and can be used to store specific tasks associated with each requirement (e.g. do a code review). You can also see the progress of all tasks associated with the requirement from the Planning > Requirements page.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Tuesday, February 8, 2011
  • Last Reply: Tuesday, February 8, 2011
  • Replies: 1
  • Views: 5480