You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Test Repository versus Test Sets

Test Sets are simple, flat lists of Tests that you can use as basis for creating Test Executions or Test Plans. Since the Tests are grouped in some logical way (e.g., grouping all Tests related with regression testing or security or all Tests for a specific component or some high-level feature/business case), a Test can be part of different Test Sets. Test Sets can also be used as a dynamic way to cover requirements.

The Test Repository concept, on the other hand, is similar to the same way you would organize your documents and files in your computer.

Each approach offers advantages and have some possible drawbacks, but they can also work in a complementary way. If used properly, you can use both in more advanced usage scenarios such as using Test Sets to cover complex requirements and using the Test Repository to organize the Tests.



ProsCons
Fields / Labels
  • Super Flexible
  • JIRA native feature
  • Allows multiple categorization simultaneously


  • No hierarchical organization
  • More complex to navigate into different categories 
  • More complex to have an overview of all categories
Test Sets
  • Can be used as a dynamic way to cover requirements
  • A test can be organized into multiple test sets
  • No hierarchical organization
  • Less intuitive way to organize, you need to create a new issue type
Test Repository
  • Hierarchical concept, similar to computer file systems,
  • Easier to understand (especially for users coming from legacy Test Management tools)
  • Can operate alongside with Test Sets & Fields
  • A Test can only be in one folder 
  • It does not allow categorized in multiple ways simultaneously 



  • No labels