Recommendation for cross-product testing

Monday, April 4, 2022
Avatar

Hi there,

We have a broad set of products and use SpiraTeams to track requirements, test cases, releases and so on.

We often have to create regression test suites that span products, for example to verify support for new OS versions or if we have a large multi-product release. 

We are in the planning phase for a large requirements restructure but what is the recommendation on how we should store requirements so that we can create test suites that span products?  We will need to be able to easily manage cross-product testing and report on test runs and incidents.

Will Programs work here?  Or Portfolios?  I'm unclear of the difference (other than Portfolios require SpiraPlan).

Thanks in advance.

Don

2 Replies
Tuesday, April 5, 2022
Avatar
re: don_mckelvie Monday, April 4, 2022

Hi, Don!

I support you with your question. We have similar problems. See please my topic Include a tesCase from one project into a testSet in another - Inflect (inflectra.com)

 

Another proposal to Inflectra was to allow eny associations between any Spira' entiities and allow to add custom association's types.

Tuesday, April 5, 2022
Avatar
re: ilyapolyakov Tuesday, April 5, 2022

The recommended approach is to use Product Associations:

https://spiradoc.inflectra.com/Spira-Administration-Guide/Product-General-Settings/#product-associations

That way you can share requirements across projects/products:

https://spiradoc.inflectra.com/Spira-User-Manual/Requirements-Management/#viewing-requirements-from-shared-products

You can then create a separate integration project that contains the test cases that map to the requirements from the other specific projects that have shared their requirements with this integration project/product.

Statistics
  • Started: Monday, April 4, 2022
  • Last Reply: Tuesday, April 5, 2022
  • Replies: 2
  • Views: 226