Recommendation for cross-product testing

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.

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.

Hello,

Good news, we have released new functionality that lets you have test cases in multiple products live in the same test set in a different product. The documentation on cross-product test sets is in SpiraDocs.

Regards

David

Dear Don,

Export a Test Set to another product functionality is now available starting from Spira v.8.12This will copy the Test Set along with its Test Cases and Test Steps. 

For more information please refer to the documentation here:
https://spiradoc.inflectra.com/Spira-User-Manual/Test-Set-Management/#exporting-a-test-set-to-a-different-product

Please log a support ticket if you need more assistance.

Regards,
Victoria -

When planning a large requirements restructure that involves cross-product regression testing, the key is to organize requirements in a way that enables traceability, reuse, and flexible grouping across multiple products. Instead of siloing requirements strictly by product, consider structuring them into shared and product-specific components, using a hierarchical or modular approach. This allows common requirements (such as OS compatibility or shared features) to be linked across products, making it easier to build unified test suites.  

Hi Don,

Yes—this is exactly the kind of scenario where Programs vs Portfolios matters, and the distinction is important.

• Programs (SpiraTeam/SpiraTest level) are best when you want to group multiple products together for shared testing and reporting (like regression suites across products or OS compatibility testing). They allow you to keep separate products but still run unified test sets and track results across them.

• Portfolios (SpiraPlan) go a step further and are more about strategic management across multiple programs/projects, including higher-level reporting, planning, and governance.

For your use case—cross-product regression testing and shared test suites—Programs are usually the right fit, because they let you:

• Organize shared requirements or test cases across products

• Build regression test sets that span multiple products

• Report on executions and incidents in a unified way

A good structure is often:

• Keep requirements primarily at product level

• Create shared or linked test cases for cross-product scenarios

• Use Programs to assemble and execute regression suites across those products

It’s a bit like удалить лишние объекты с фото you’re not changing each product separately, but carefully removing boundaries where needed so you can focus only on the relevant shared elements for regression testing and reporting.