Test Management - Use Case

[Tommaso2]

Hi all,

- Can you please provide an end-to-end use case for Test management that goes through all the features?

So test, test set, test plan, test cycle, test execution suites.

- I saw that "Test execution suites" can be also triggered from the project: how it works?

Many thanks,
Tommaso

[Chai Maddula · Accepted solution]

Hi @Tommaso2 

The Test Management 2.0 module supports the following flow for testing. Start by creating a test plan describing how a product or feature needs to be tested. Further, split the test plan into test cycles and test cycles into test execution sets. Test Sets are comprised of individual tests and added to test suites.

Example of a Test Plan Structure: 
The following flowchart provides a sample test plan developed for a software project deployment in Test Management 2.0. This graphic illustrates the use of a test plan, test cycles, and execution suites. The test plan has two test cycles: a test cycle for system testing and a test cycle for user acceptance testing. The system test cycle has three test execution suites to test IT Service Management, Integrations, and Core functionality. The user acceptance testing cycle also has test execution suites for testing Incident Management, Change Management, and Knowledge Management. Individual tests are assigned to the test execution suites. Projects may have one or more test plans as determined by the Test Manager.

Example of a Test Plan Structure:

The following flowchart provides a sample test plan developed for a software project deployment in Test Management 2.0. This graphic illustrates the use of a test plan, test cycles, and execution suites.

The test plan has two test cycles: a test cycle for system testing and a test cycle for user acceptance testing. The system test cycle has three test execution suites to test IT Service Management, Integrations, and Core functionality. The user acceptance testing cycle also has test execution suites for testing Incident Management, Change Management, and Knowledge Management. Individual tests are assigned to the test execution suites.

Projects may have one or more test plans as determined by the Test Manager

If my response solves your query, please marked helpful by selecting Accept as Solution and Helpful

[GlideFather]

Hi @Tommaso2,

Each feature will be tested differently and also client by client will have a different test steps.

I don't think there is any general answer to this or do you have any details to share what is your exact goal?

[Chai Maddula · Accepted solution]

Hi @Tommaso2 

The Test Management 2.0 module supports the following flow for testing. Start by creating a test plan describing how a product or feature needs to be tested. Further, split the test plan into test cycles and test cycles into test execution sets. Test Sets are comprised of individual tests and added to test suites.

Example of a Test Plan Structure: 
The following flowchart provides a sample test plan developed for a software project deployment in Test Management 2.0. This graphic illustrates the use of a test plan, test cycles, and execution suites. The test plan has two test cycles: a test cycle for system testing and a test cycle for user acceptance testing. The system test cycle has three test execution suites to test IT Service Management, Integrations, and Core functionality. The user acceptance testing cycle also has test execution suites for testing Incident Management, Change Management, and Knowledge Management. Individual tests are assigned to the test execution suites. Projects may have one or more test plans as determined by the Test Manager.

Example of a Test Plan Structure:

The following flowchart provides a sample test plan developed for a software project deployment in Test Management 2.0. This graphic illustrates the use of a test plan, test cycles, and execution suites.

The test plan has two test cycles: a test cycle for system testing and a test cycle for user acceptance testing. The system test cycle has three test execution suites to test IT Service Management, Integrations, and Core functionality. The user acceptance testing cycle also has test execution suites for testing Incident Management, Change Management, and Knowledge Management. Individual tests are assigned to the test execution suites.

Projects may have one or more test plans as determined by the Test Manager

If my response solves your query, please marked helpful by selecting Accept as Solution and Helpful

[SD_Chandan · Accepted solution]

HI @Tommaso2 ,

Test cases always differ based on the module, client, and specific requirements. There's no one-size-fits-all. Each client may have unique workflows, UI policies, roles, or customizations—so test cases need to be tailored accordingly. It's best to understand the exact use case before preparing or reusing any test scenario

End-to-End Test Management Use Case.

Example of SRM module 
Test Case – Define what to test (e.g., SRM request creation, approval, fulfillment). Include steps, expected results, and variables.
Test Set – Group related test cases (e.g., SRM workflows, UI policies, field access).
Test Plan – Outline strategy, scope, and link test sets.
Test Cycle – Represents a phase like UAT or Regression. Attach test plans here.
Test Execution Suite – Run tests, track results, and log defects. Can be triggered manually or from a Project Task when it reaches a testing stage.

Triggering from Project
You can link a Test Execution Suite to a Project or Story. When the task moves to "Ready for Testing," the suite can auto-trigger using Flow Designer or Business Rules.

SRM Module Testing Tips
Raise request as end user
Approver approves → Fulfillment group acts
Validate:
Variable workflows
UI Policies
Stage transitions
Field access (based on roles/client setup)

Hope you find this information helpful..!