- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2025 09:05 AM
Hi all,
About integration between Demand and Test Management in ServiceNow:
- When tests are needed in a demand if it is not about execution?
- How tests can be an automated step of demand process? Because based on my understanding, Test Management is a standalone process
Many thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2025 10:06 PM - edited 07-20-2025 10:06 PM
Hi @Tommaso2 ,
1. When are tests needed in a Demand if it’s not about execution?
The Demand phase is about idea capture, assessment, prioritization, and approval — not execution. However, tests may be involved in these scenarios:
Use Cases Where Tests Are Relevant Before Execution:
Feasibility Testing (Pre-Project PoC):
Lightweight tests to validate that a concept or proposed solution works.
Often done during technical assessment of a demand.
Example: API connectivity, sandbox proof-of-concept.
Risk or Impact Assessment:
Running tests to understand potential regression impacts of implementing a new feature.
Often seen in infrastructure or platform-related demands.
Stakeholder Confidence:
Demonstrating working examples or prior test runs to justify prioritization.
In these cases, you're not doing a full QA cycle, but rather leveraging Test Cases/Plans for technical validation to support the business case of the demand.
2. How can tests be an automated step in the Demand process if Test Management is standalone?
With a bit of automation and configuration, you can integrate it into the demand lifecycle.
Ways to Integrate Tests into the Demand Process:
A. Custom Flow or Script to Trigger Test Plan
Use Flow Designer or a Business Rule on Demand.
When the demand enters a certain state (e.g., "Assessment" or "Qualified"), create a Test Plan and link it.
B. Extend Demand Form with Related Test Cases
Add a related list or embedded list to display related Test Cases or Test Plans.
Use a custom M2M relationship if needed.
Embed Test Results into Demand Assessment
Once a Test Plan is run (manual or automated), you can:
Display summary test results in the demand record.
Update a custom field like u_test_result = Passed/Failed.
Gate approval or scoring based on test result.
D. Use ATF (Automated Test Framework) to Validate Pre-conditions
If your demand requires validation of platform features (e.g., performance or UI tests), link it to ATF test runs.
ATF can be triggered via script and results logged into a demand-related custom table.
If my response helped please mark it correct or Helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2025 10:06 PM - edited 07-20-2025 10:06 PM
Hi @Tommaso2 ,
1. When are tests needed in a Demand if it’s not about execution?
The Demand phase is about idea capture, assessment, prioritization, and approval — not execution. However, tests may be involved in these scenarios:
Use Cases Where Tests Are Relevant Before Execution:
Feasibility Testing (Pre-Project PoC):
Lightweight tests to validate that a concept or proposed solution works.
Often done during technical assessment of a demand.
Example: API connectivity, sandbox proof-of-concept.
Risk or Impact Assessment:
Running tests to understand potential regression impacts of implementing a new feature.
Often seen in infrastructure or platform-related demands.
Stakeholder Confidence:
Demonstrating working examples or prior test runs to justify prioritization.
In these cases, you're not doing a full QA cycle, but rather leveraging Test Cases/Plans for technical validation to support the business case of the demand.
2. How can tests be an automated step in the Demand process if Test Management is standalone?
With a bit of automation and configuration, you can integrate it into the demand lifecycle.
Ways to Integrate Tests into the Demand Process:
A. Custom Flow or Script to Trigger Test Plan
Use Flow Designer or a Business Rule on Demand.
When the demand enters a certain state (e.g., "Assessment" or "Qualified"), create a Test Plan and link it.
B. Extend Demand Form with Related Test Cases
Add a related list or embedded list to display related Test Cases or Test Plans.
Use a custom M2M relationship if needed.
Embed Test Results into Demand Assessment
Once a Test Plan is run (manual or automated), you can:
Display summary test results in the demand record.
Update a custom field like u_test_result = Passed/Failed.
Gate approval or scoring based on test result.
D. Use ATF (Automated Test Framework) to Validate Pre-conditions
If your demand requires validation of platform features (e.g., performance or UI tests), link it to ATF test runs.
ATF can be triggered via script and results logged into a demand-related custom table.
If my response helped please mark it correct or Helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2025 12:29 AM
Hi!
Very useful!
Thank you