Test Management

[Tommaso2]

Hi all,

Which are the main differences between General Testing and Sprint Testing?

Can you please provide real examples?

I read the standard definition but it is still unclear.

Additionally, I wonder how UAT are managed in Test Management.

many thanks,

Tommaso

[iekosmadakis · Accepted solution]

Hello @Tommaso2 !
General Testing and Sprint Testing differ mainly in scope, timing, focus and the people involved.

General Testing is broader in nature and typically occurs after development is complete or at key milestones. It focuses on system-wide stability, integration and regression. It's commonly performed by QA teams or end users during UAT. For example (speaking in SN terms), it may involve testing the full Incident Management module after all enhancements or running regression tests on Change workflows post-upgrade.

In contrast, Sprint Testing is aligned with Agile sprints and targets only the new features or user stories developed within that sprint. It focuses on validating functionality against acceptance criteria and is usually conducted by the sprint team (developers, QA or even Product Owners). Real examples include (again using SN terms) testing a new UI Policy for Incident records, verifying a Script Include for an API call or validating a new Catalog Item created during the sprint.

So, General Testing supports broader quality assurance while Sprint Testing ensures iterative delivery validation.

Please consider marking my answer as helpful and accepting it as the solution if it assisted you in any way.

[Tommaso2]

Hi!

Thank you for your reply.

I also found this sentence in the official documentation that is quite confusing to me:

• Scaled Agile Framework (SAFe) to provide testing capabilities in SAFe. As a result of this integration, you can verify and pass the acceptance criteria of SAFe stories by creating and running tests in SAFe Board.
• Agile Development 2.0 to add testing capabilities to Agile development.
• Project Portfolio Management (PPM) with Financials adds the ability to associate a Test Phase in a project to Test Execution Suites in Test Management 2.0. 

1. SAFe: it is an extra integration right? It is not in scope with Test Management?

2. As far as I understood, Agile development is related both to SPM and ITSM. In both cases you can use agile board to manage stories, but it is not clear to me how agile is concretely triggered in the platform.

E.g. SPM: A new project is created and I can create new stories in the agile board for the release?

E.g. ITSM: A new change is developed and I can create new stories in the agile board for the release?

3. Last bullet point mentions "new test phase" in projects, but how it works? 

It is an extra functionality in addition to the agile board?

Moreover, Test Management is now only available in 2.0 version? Same for Agile development?

many thanks and regards,

Tommaso