Thread

Skip Navigation LinksForums > SpiraTest Forums > SpiraTest Best Practices > Multiple Projects Vs. Sin...

Multiple Projects Vs. Single Project for Related Systems RSS Feed

Tuesday, February 8, 2011

We have an array of related products that share many of the same requirements and test cases. Since SpiraTest treats projects as independent entities, we cannot easily share requirements and test cases between them. Should we consider using a single project?

5 Replies
Adam SAdam S
re: Adam S on Tuesday, February 8, 2011
Tuesday, February 8, 2011

Generally we recommend using a single large project if the various products are highly related and share the same requirements and test cases. This can be done by simply making each project it's own separate Release Tree. So in the Release Hierarchy you'd have:

  • Product 1
    • Release 1
      • Iteration 1
      • Iteration 2
    • Release 2
      • Iteration 1
      • Iteration 2
  • Product 2
    • Release 1
      • Iteration 1
      • Iteration 2
    • Release 2
      • Iteration 1
      • Iteration 2
  • Product 3
    • Release 1
      • Iteration 1
      • Iteration 2
    • Release 2
      • Iteration 1
      • Iteration 2

On the other hand, if your products are largely independent of each other, we would recommend using separate projects to keep things simple.

Thomas HartmannThomas Hartmann
re: Adam S on Tuesday, February 8, 2011
Tuesday, March 8, 2011
If I follow your suggestion to define all similar products as a release in a project, then I still have the problem that I can assign requirements only to one single release, but a common requirement shall be valid in all releases/products ! How does sharing of requirements work in this context ?
Adam SAdam S
re: Thomas Hartmann on Tuesday, March 8, 2011
Tuesday, March 8, 2011
Could you create a "Common" release for any of the requirements that are common between the products?
Thomas HartmannThomas Hartmann
re: Adam S on Tuesday, March 8, 2011
Wednesday, March 9, 2011

Creating a common release is a theorte

Thomas HartmannThomas Hartmann
re: Adam S on Tuesday, March 8, 2011
Wednesday, March 9, 2011
Creating a common release is a theoretical solution (not likely to be done in our case), meaning that each product is based on a release of the common release !? If this is the case, then this doesn`t prevent me to do some kind of regression testing for a product release which requires also retesting of the "common" release requirements. And this is not supported !
Tagged
Statistics
  • Started: 2/8/2011
  • Last Reply: 3/9/2011
  • Replies: 5
  • Views: 1957
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2016 | Licensed to Inflectra Corporation.