| Test | Description | Release version |
|---|---|---|
| Verify that global rank is populated when a story is created | Verify the global rank of a story after creation. | Madrid |
| Verify that closing a sprint with active stories is prevented | Verify that a sprint with active stories cannot be closed. | Madrid |
| Verify that sprints cannot overlap in the same group | Verify that sprints in the same group do not overlap. | Madrid |
| Verify that sprint points are updated | Verify that changes to stories produce accurate sprint point totals. | Madrid |
| Verify that only one sprint in a group can have the current state | Verify sprint statuses. | Madrid |
| Verify sprint end date is after the sprint start date | Verify sprint start and end dates. | Madrid |
| Verify that any update on story rolls up to Epic | Verify that adding, estimating, removing, deleting, updating, or cancelling a story updates the epic-level roll-ups correctly. | Orlando |
| Verify changes to the scope of a current sprint do not alter the value of the Total Committed Points | Verify that the value of Total Committed Points does not change with change in the scope of a sprint after its state is changed to Current. | Orlando |
| Verify active flag is set false when Agile Story state is changed to Completed/Cancelled | Verify that active flag of an Agile story is set to the following: - False, if the state is changed to Completed or Cancelled - True, for all other states | Orlando |
| Verify that updating the team/group capacity overrides the capacity on all the future sprints | Verify that any update to the **Group capacity** field of the assignment group results in the following changes to the **Group capacity** field of the various sprints associated with this assignment group: - For the sprints that are in the Draft and Planning state: - The group capacity is updated to the new value. - The **Group capacity** field is editable. - For the sprints in the Current, Complete, or Cancelled state: - The group capacity remains the old value. - The **Group capacity** field is read-only. For the sprints in the Draft or Planning state, you can individually edit the group capacity of the sprint anytime later. This would not change the group capacity of the assignment group associated with this sprint. | Paris |
| Verify create and edit functionality of an epic backlog on the scrum program board | - Verify that you can create an epic backlog for scrum programs from the Backlog tab of Agile Board. - Verify that you can update an existing epic backlog for scrum programs from the Backlog tab of Agile Board. - The epics listed in the backlog must belong to the selected epic backlog. | Quebec |
| Verify a Demand is converted to a scrum story | If the PPM Standard plugin \(com.snc.financial\_planning\_pmo\) is active, verify that a Demand can be converted to an Agile 2.0 story using the **Create Story** related link on the Demand form. For more information on how to create an Agile 2.0 story from a demand, see [Create an artifact from a demand](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/t_CrtArtftDmdMnu.md). | Quebec |
| Verify a Demand is converted to a scrum epic | If the PPM Standard plugin \(com.snc.financial\_planning\_pmo\) is active, verify that a Demand can be converted to an Agile 2.0 epic using the **Create Epic** related link on the Demand form.For more information on how to create an Agile 2.0 epic from a demand, see [Create an artifact from a demand](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/t_CrtArtftDmdMnu.md). | Quebec |
| Test | Description | Release version |
|---|---|---|
| CMDB HEALTH: Health Job Status | Checks whether any CMDB Health dashboard jobs, which were started 30 or more days ago, are still in progress. | New York |
| CMDB HEALTH: CMDB Health Completeness/ Recommended | Checks whether the recommended metric \(included in the CMDB Health completeness KPI\) is fully functional.This test validates: - Creation of a health inclusion rule for the recommend metric. - Creation of a recommended field that satisfies the health inclusion rule. - Validate that the health inclusion rule is correctly applied to a test record with missing data in the recommended field. | New York |
| Test | Description | Release version |
|---|---|---|
| CMDB IRE: IRE Validation | Validate CI identifiers and reconciliation definitions and check indexes for CI identifiers. | Madrid |
| CMDB IRE: Reconciliation Rule | Check operations on a reconciliation rule, in CI Class Manager, using sn\_cmdb\_editor, sn\_cmdb\_admin, itil, and itil\_admin roles. Operations include create, edit, and delete a reconciliation rule. Also, check for active and not active setting, and derived rules. | Paris |
| CMDB IRE: Identification Rule | Check operations on an identification rule, in CI Class Manager, using sn\_cmdb\_editor, sn\_cmdb\_admin, itil, and itil\_admin roles. Operations include create, edit, and delete an identification rule. Also, check for active and not active setting, and derived rules. | Paris |
| Test | Description | Release version |
|---|---|---|
| CSM: Create Product Case | Create a case for a product. | Madrid |
| CSM: Assign Case to an Agent | Create a case and assign it to a customer service agent. | Madrid |
| CSM: Assign Asset on Case | Assign an asset to a case. | Madrid |
| CSM: Assign Entitlement | Assign an entitlement to a case. | Madrid |
| CSM: Escalate an Account | Escalate an account. | Madrid |
| CSM: Escalate a Case | Escalate a case. | Madrid |
| CSM: Create Special Handling Notes | Create special handling notes for a case. | Madrid |
| CSM: Close a Case | Close a case. | Madrid |
| CSM: Time Recording | Record the time worked on a case. | Madrid |
| CSM: Create CHG from Case | Create a change record from a case. | Madrid |
| CSM: Create Incident from Case | Create an incident record from a case. | Madrid |
| CSM: Create Order Case | Create a case for an order. **Note:** Requires Customer Service Management for Orders. | Madrid |
| CSM - Create Order Case as Customer from CSM Portal | Create an order case as a customer from the Customer Service Portal. **Note:** Requires the Customer Service Portal. Also requires that the test be run as admin. | Madrid |
| CSM: Create Problem from Case | Create a problem record from a case. | Madrid |
| CSM: Create Major Case and its Child Cases | Create a major case and the associated child cases for the customer accounts in the recipient list. **Note:** Requires Major Issue Management. | Orlando |
| CSM: Agent Creating Request for Customer | As a customer service agent, create a request for a customer. **Note:** Requires Customer Service Request Integration. | Orlando |
| CSM: Register New Case Type | Register a case type and verify the record is created. | Orlando |
| CSM - Create Project for an Account | Project Manager creates project for an account.**Note:** Requires Customer Project Management. | Orlando |
| CSM - Identify Project Contact | Project manager identifies customers to a project.**Note:** Requires Customer Project Management. | Orlando |
| CSM - Create Case from Project | Create a case from a project. | Orlando |
| CSM: Advanced Type Skill Determination Rule Test | Create an advanced type skill determination rule. **Note:** Requires Skill Determination. | Orlando |
| CSM - Create Case from Project Task | Create a case from a project task. | Orlando |
| CSM: Create Task from Case | Create a case task from a case. | Orlando |
| CSM: Assign Case Task to Case Task Agent | The customer service agent creates and assigns a case task to a case task agent. | Rome |
| CSM: Case Task Agent views assigned Case Task | Verifies that the case task agent can view an assigned case task. | Rome |
| CSM: Case Task Agent Completes Assigned Task | The case task agent completes an assigned case task. | Rome |
| CSM-Create a case using 'Create a case \(POST\)' API | Create a case using 'Create a case \(POST\)' API.**Note:** Requires a user authentication record assigned to the **Basic authentication** field in step 1 of the ATF. | Rome |
| CSM-Query a case using 'Query a case \(GET\)' API | Query a case using 'Query a case \(GET\)' API.**Note:** Requires a user authentication record assigned to the **Basic authentication** field in step 1 of the ATF. | Rome |
| CSM: Address sharing across Accounts | Implement reusable addresses for accounts to support complex customer operations and business models. | Washington DC |
| CSM: Manage Consumer Profile Locations | Create and manage consumer locations, and map them to consumer profiles. | Washington DC |
| CSM: OCS Manager creating New OSP | Verify that a new Outsourced Service Provider \(OSP\) is created by the OCS internal manager. **Note:** Requires Outsourced Customer Service. | Rome |
| CSM: Case Creation by OCS Agent | Verify that an Outsourced Customer Service agent is able to create a case. **Note:** Requires Outsourced Customer Service. | Rome |
| CSM - Create Proactive Case by NOC Operator | Verify whether a proactive case is created.**Note:** Requires Proactive Customer Service Operations with Event Management. | New York |
| CSM - Employee creating case OBO customer | As an employee with the proxy contact role \(sn\_customerservice\_proxy\_contact\), create a case from the self-service portal on behalf of a customer. **Note:** Requires the CSM Extension for Proxy Contacts. | New York |
| CSM - Lookup Type Skill Determination Rule Test | Create a lookup type skill determination rule.**Note:** Requires Skill Determination. | New York |
| CSM - Manager creating request OBO customer from CSM portal | As a user with the case manager role, create a case on behalf of a customer from the Customer Service Portal.**Note:** Requires Customer Service Request Integration. | New York |
| CSM - Simple Type Skill Determination Rule Test | Create a simple type skill determination rule.**Note:** Requires Skill Determination. | New York |
| CSM - Project Manager create project task and assign to a customer | Project manager creates project task and assigns to a customer.**Note:** Requires Customer Project Management. | Orlando |
| CSM - Agent Create Cases from a Project | As a customer service agent, create a case from a project.**Note:** Requires Customer Project Management. | Orlando |
| CSM - Agent Create Cases from a Project task | As a customer service agent, create a case from a project task.**Note:** Requires Customer Project Management. | Orlando |
| CSM - Agent Create Change Requests for a project | As a customer service agent, create a change request for a project. | Orlando |
| CSM - Service Contracts covered under Sold Product | Create sold products and service contracts and associate service contracts to a sold product. Verify the association between the active contracts and the sold product.**Note:** Requires Customer Service Install Base Management. | Orlando |
| AWA - Create New Service Channel | Create a new service channel in the Advanced Work Assignment application. **Note:** Requires Advanced Work Assignment for CSM. | Orlando |
| CSM-ITOM - Create Child Cases for Proactive Major Case | Create a child case for a proactive major case using recipient list.**Note:** Requires Proactive Customer Service Operations with Event Management. | Orlando |
| CSM - Create Outage from Case | Validate if newly created outage is linked to a case. | Paris |
| CSM: Create Sold Product on Household | Create a sold product on a household and its member. **Note:** Requires Customer Service Install Base Management and Customer Household Data Model with **Load demo data** enabled. | Quebec |
| CSM: View Health Status of Install Base Item from Account and Case pages | Validates the functionality of the **Refresh Install Base Health** button on the Account and Case record pages. | Quebec |
| CSM: Report a knowledge gap from a case in Agent Workspace | Verify that a knowledge gap related to a case was reported in Agent Workspace | Rome |
| CSM-Create a case using 'Create a case \(POST\)' API | Create a case using 'Create a case \(POST\)' API.**Note:** Requires a user authentication record assigned to the **Basic authentication** field in step 1 of the ATF. | Rome |
| CSM-Query a case using 'Query a case \(GET\)' API | Query a case using 'Query a case \(GET\)' API.**Note:** Requires a user authentication record assigned to the **Basic authentication** field in step 1 of the ATF. | Rome |
| CSM: OCS Manager creating New OSP | Verify that a new Outsourced Service Provider \(OSP\) is created by the OCS internal manager. **Note:** Requires Outsourced Customer Service. | Rome |
| CSM: Case Creation by OCS Agent | Verify that an Outsourced Customer Service agent is able to create a case. **Note:** Requires Outsourced Customer Service. | Rome |
| CSM: Manage Consumer Profile Locations | Create and manage consumer locations, and map them to consumer profiles. | Washington DC |
| CSM: Address sharing across Accounts | Implement reusable addresses for accounts to support complex customer operations and business models. | Washington DC |
| CSM: Create Case as Location Contributor from BLSP Portal | As a location contributor,create a case from the BLSP portal. | Yokohama |
| CSM: Create a Business Location And Onboard a Member To It | Verifies the creation of a business location and onboarding a member to it. | Yokohama |
| CSM: Escalate or de-escalate account workflow | Escalate or de-escalate account workflow | Zurich |
| Test | Description | Release version |
|---|---|---|
| CSM - Create Product Case as Customer from CSM Portal | Create a product case as a customer from the Customer Service Portal.**Note:** Requires Customer Service Portal. Also requires that the test be run as admin. | Madrid |
| CSM - Create Product Case as Partner from CSM Portal | Create a product case as a partner from the Customer Service Portal.**Note:** Requires Customer Service Portal. Also requires that the test be run as admin. | Madrid |
| CSM - Search on Homepage | Search for information from the Customer Service Portal. The search includes cases, Knowledge articles, and Community threads. | New York |
| CSM - Update Support Profile | Update a contact's profile from the Customer Service Portal. | New York |
| CSM - Provide requested info on case | From the Customer Service Portal, the contact can provide information for a case that was requested by the agent. | New York |
| CSM - Accept Proposed Solution On Case | Accept a proposed solution for a case from the Customer Service Portal. | New York |
| CSM - Provide Feedback on Survey | Provide feedback on a survey after a case is closed from the Customer Service Portal. | New York |
| CSM - View All Desktop Notifications | View all Customer Service Management specific desktop notifications. | Orlando |
| CSM - View Publications on CSM Portal | View publications on the Customer Service Management portal. | Orlando |
| CSM - Create Contact on CSM Portal | Create contacts on the Customer Service Management portal. | Orlando |
| CSM: Validate Outage widgets in CSM Portal | Validates various types of outages and the corresponding widgets shown on the Customer Service Portal home page and the Install Base page. | Quebec |
| CSM - Create case from Portal as Consumer Contributor | Creates a customer case from the portal by a user with the consumer contributor user role \(sn\_customerservice.consumer\_contributor\).**Note:** Requires Business Location, Customer Household Data Model, and CSM Contributor User. | Rome |
| CSM - Create case from Portal as Account Contributor | Creates a customer case from the portal by a user with the account contributor user role \(sn\_customerservice.account\_contributor\).**Note:** Requires Business Location, Customer Household Data Model, and CSM Contributor User. | Rome |
| CSM - Add related parties on Case and perform action on case as Related party | Verify the ability to add related parties to the case and perform actions on the case as related parties through the CSM Portal. | Rome |
| CSM - Create product case as an account consumer from the CSM Portal | Create a product case as an account from the customer service portal.**Note:** Requires Customer Service Portal. Also requires that the test be run as admin. | Australia |
| Test | Description | Release version |
|---|---|---|
| CSP - Create product case as consumer from CSP Portal | Create a product case as a consumer from the Consumer Service Portal. **Note:** Requires the Consumer Service Portal. Also requires that the test be run as admin. | Madrid |
| CSP - Search on homepage | Search for information from the Consumer Service Portal. The search includes cases, knowledge articles, and Community threads. | New York |
| CSP - Update support profile | Update a consumer's profile from the Consumer Service Portal. | New York |
| CSP - Register your product | Register a product from the Consumer Service Portal. | New York |
| CSP - Provide requested info on case | From the Consumer Service Portal, the consumer can provide information for a case that was requested by the agent. | New York |
| CSP - Accept proposed solution on case | Accept a proposed solution for a case from the Consumer Service Portal. | New York |
| CSP - Provide feedback on Survey | Provide feedback on a survey after a case is closed from the Consumer Service Portal. | New York |
| CSP - View publications on CSP Portal | View publications on Customer Service portal. | Orlando |
| CSP - Create product case as an internal unified consumer from CSP Portal | This test verifies the functionality of creating a product case as an internal unified consumer from the CSP portal in conjunction with the Customer Service and Consumer Service Portal plugins, using the Customer Service Management \(CSM\) demo data plugin. | Yokohama |
| CSP - Create product case as an external unified consumer from CSP Portal | This test verifies the functionality of creating a product case as an external unified consumer from the CSP portal in conjunction with the Customer Service and Consumer Service Portal plugins, using the Customer Service Management \(CSM\) demo data plugin. | Yokohama |
| CSP - Create household member as an account consumer from the CSM Portal | Create a household member as an account from the customer service portal.**Note:** Requires Customer Service Portal. Also requires that the test be run as admin. | Australia |
| Test | Description | Release version |
|---|---|---|
| CSM Walkup: Check-in as a walkup user, look at the queue, and submit a survey | As a walk-up user, perform check-in, look at the queue, and submit feedback through a survey.**Note:** This test works when the Seattle location, available with demo data, is available. | Rome |
| Test | Description | Release version |
|---|---|---|
| Create Adhoc Delegation for Approval Task | Ensures an adhoc delegation for an approval task can be created from the My Tasks form in the Employee Center. | San Diego |
| Create Adhoc Delegation for HR Task | Ensures an adhoc delegation for an HR task can be created from the My Tasks form in the Employee Center. | San Diego |
| Employee Center - My Favorites | Verifies the favorite functionality in the Employee Center. Also verifies when a KB article or catalog item is added to the Favorite widget. | San Diego |
| Employee Center - Approval Hub Approve Request | Verifies the approval functionality in the Employee Center. Also verifies that when a request is approved, it appears in the user's **Completed** column. | San Diego |
| Employee Center - Approval Hub Reject Request | Verifies the rejection functionality. Also verifies that when a request is rejected, it appears in the user's **Completed** column. | San Diego |
| Employee center - Employee Profile Generation | Verifies that employee profiles are generated as per the employee definition. | Xanadu |
| Employee Center - Topic Page | Associates a KB article or catalog item to a topic and verifies they display on the topic page. | San Diego |
| Employee Center - Validate home page widgets | Validates the following widgets are present on the Employee Center home page:- Relevant for you - Popular topics - My Active Items - Quick tasks - Homepage Search | San Diego |
| ESC: Employee can see ticket updates | Employees can view updates to their tickets. | Quebec |
| ESC: Post General HR Inquiry questions on ESC portal | Verifies an HR employee can create a General Inquiry case and post general HR inquiry questions on the ESC. | Quebec |
| ESC: Submit a Record Producer which creates Universal Request and HR Case | Verifies a user can submit an HR catalog item that creates a Universal Request. Also verifies the Universal Request and HR case are created and linked. | Quebec |
| ESC: Verify Standard Ticket page on ESC for HR Case | Creates a general inquiry case from the service portal and verifies it appears on the standard Ticket page. | Quebec |
| ESC: Verify widget contents in Catalog items | Verifies the widget content in a Catalog page. | Orlando |
| ESC: Verify widget contents in knowledge pages | Verifies the widget content in a Knowledge page. | Orlando |
| HR: Search catalog items & KBs in ESC | Verifies the search functionality in the ESC. | Quebec |
| Taxonomy and Topic Creation | Creates taxonomy and topics and then adds content to the topic. | San Diego |
| Test | Description | Release version |
|---|---|---|
| Essential SAFe: Feature tests | Verify feature global rank updates. | Madrid |
| Essential SAFe: Feature tests | For a SAFe feature, verify that: - Actual start date is populated after the state is changed to Implementation, Validation on Staging, or Deployment. - Actual end date is populated after the state is changed to **Released** or **Cancelled**. - Active flag is set to the appropriate value: - **False**, if the state is changed to **Released** or **Cancelled**. - **True**, for all other states. | Orlando |
| Essential SAFe: Feature tests | If the PPM Standard plugin \(com.snc.financial\_planning\_pmo\) is active, verify that a Demand can be converted to a SAFe feature using the **Create SAFe Feature** related link on the Demand form. For more information on how to create an SAFe feature from a demand, see [Create an artifact from a demand](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/t_CrtArtftDmdMnu.md). | Quebec |
| Essential SAFe: Program increment tests | Verify program increment date overlapping. | Madrid |
| Essential SAFe: Sprint tests | Verify the generation of ART sprints and team sprints as well as updates to sprint points and dates. | Madrid |
| Essential SAFe: Sprint tests | Verify that any update to the **Group capacity** field of the assignment group results in the following changes to the **Group capacity** field of the various sprints associated with this assignment group: - For the sprints that are in the **Draft** or **Planning** states: - The group capacity is updated to the new value. - The **Group capacity** field is editable. - For the sprints in the **Current**, **Complete**, or **Cancelled** states: - The group capacity remains the old value. - The **Group capacity** field is read-only. For the sprints in the **Draft** or **Planning** state, you can individually edit the group capacity of the sprint anytime later. This would not change the group capacity of the assignment group associated with this sprint. | Paris |
| Essential SAFe: Story tests | Verify story global rank updates. | Madrid |
| Essential SAFe: Story tests | Verify that active flag of the SAFe story is set to the appropriate value: - **False**, if the state of the state is changed to Completed or Cancelled. - True, for all other states. | Orlando |
| Essential SAFe: Story tests | Verify that adding, estimating, removing, deleting, updating, or cancelling a SAFe story updates the SAFe feature-level and then the epic-level roll-ups correctly. | Orlando |
| Essential SAFe: Story tests | Verify that adding, updating, or deleting the feature on a SAFe story updates the Epic field on the SAFe story form. | Orlando |
| Essential SAFe: Story tests | If the PPM Standard plugin \(com.snc.financial\_planning\_pmo\) is active, verify that a Demand can be converted to a SAFe story using the **Create SAFe Story** related link on the Demand form. For more information on how to create a SAFe story from a demand, see [Create an artifact from a demand](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/t_CrtArtftDmdMnu.md). | Quebec |
| Essential SAFe: Team tests | Verify team association with an ART. | Madrid |
| Essential SAFe: Epic tests | For a SAFe epic, verify that:- Actual start date is populated after the state is changed to **Implementation**. - Actual end date is populated after the state is changed to **Complete**. - Active flag is set to the appropriate value: - **False**, if the state is changed to **Released** or **Cancelled** states. - **True**, for all other states. | Orlando |
| Essential SAFe: Epic tests | If the PPM Standard plugin \(com.snc.financial\_planning\_pmo\) is active, verify that a Demand can be converted to a SAFe epic using the **Create SAFe Epic** related link on the Demand form.For more information on how to create a SAFe epic agile from a demand, see [Create an artifact from a demand](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/t_CrtArtftDmdMnu.md). | Quebec |
| Essential SAFe: Program PI Objective tests | Verify the functionality of creating and updating PI objectives- Verify that you can create a program increment-level objective - Verify that you can update the created PI objective with the planned business value \(PBV\) and actual business value \(ABV\) - Verify that the percentage of business value achieved is computed as the percentage of ABV complete for committed PI objectives compared to program PBV | Rome |
| Essential SAFe: Team PI Objective tests | Verify the functionality of creating and updating team PI Objectives- Verify that you can create a team-level PI objective - Verify that you can update the created PI objective with the planned business value \(PBV\) and actual business value \(ABV\) - Verify that the percentage of business value achieved is computed as the percentage of ABV complete for committed PI objectives compared to the team PBV in the PI | Rome |
| Test | Description | Release version |
|---|---|---|
| FSM: Create Initiate Qualify Dispatch and assign Work Order Task | - Create a work order. - Initiate and qualify a work order. - Dispatch a work order. - Assign a work order task to an agent. | Madrid |
| FSM: Part Sourcing | - Source any part to an agent's stock room from the work order task. - Create a transfer order line for the part sourcing. - Use this part for any work order to consume it using the **Part Usage** action. | Madrid |
| FSM: Part Usage | - Source any part to an agent's stock room from the work order task. - Use this part for any work order to consume it using the Part Usage action. | Madrid |
| FSM: Questionnaire | Create a questionnaire and associate it with a work order task. | Madrid |
| FSM: Field Service Configuration | Verify that the default configuration such as task assignment method, qualification requirement, PDF summary and agent's ability to accept or reject tasks is preserved. | New York |
| FSM: Planned Maintenance | Create a planned maintenance work order with weekly interval time for printer maintenance. | New York |
| FSM: Appointment Booking Configuration | Verify that the default configuration for appointment booking is preserved and that the point of sale service and catalog item exists in the system. | New York |
| FSM: Create Work or Personal Schedules | Create personal or work schedule for agents. | Orlando |
| FSM: Field Service Property Settings | Verify that the field service system properties preserve expected values. | Orlando |
| FSM: Work Groups | Verify that field service agents can be added to work groups. | Orlando |
| FSM: Dynamic Scheduling - Preferred Technician assignment with mandatory parts reservation | With Dynamic scheduling:- Preferred technician should be picked for task assignment. - Mandatory parts should be reserved in the agent stock room. **Note:** Activate Customer service management demo data plugin. | Paris |
| FSM: Create Time Card | Verify that a time card is created for an agent in the work order task. | Quebec |
| FSM: Create incidental | Verify that an incidental is created for an agent in the work order task. | Quebec |
| FSM: Onboarding contractor company | Verify that a contractor company is onboarded with assignment group, external manager, and external agent.**Note:** Activate Field Service Contractor Management plugin. | Quebec |
| FSM: Onboarding contractor agent by external manager | Verify that an external contractor manager can onboard external agents from the Field Service Contractor Management portal. | Quebec |
| FSM: External contractor manager fulfil the work order task | Verify that a contractor manager or an agent is able to fulfil the assigned work order task. | Quebec |
| FSM: Assign work order task to Vendor group | Verify that a work order task is assigned to the external assignment group based on the defined criteria, such as task location and configuration parameters. | Quebec |
| FSM: Pause and Resume work order task | Verify that an agent can pause and resume work for a work order tasks. | Rome |
| FSM: Dynamic Scheduling - Assign technician with matching skills | With Dynamic Scheduling: Verify that a work order task is assigned to a technician who possesses all mandatory skills mentioned in the task. | Rome |
| FSM: Off boarding contractor agent by external manager | Verify that an external contractor manager can off board external agents from the Field Service Contractor Management portal. | Rome |
| FSM: External contractor manager asset sourcing and usage | Verify that an external contractor manager is able to perform the following actions: - Request parts from stockroom. - Pick the part. - Close the transfer order. - Perform work using the part. | San Diego |
| FSM: External contractor agent fulfil the work order task | Verify that a contractor agent is able to fulfil the work order task that is assigned by the external contractor manager. | San Diego |
| FSM: Capacity Scheduling - Assign work to field service agents based on capacity | Verify that the rules and values mentioned in the capacity definition and capacity assignment module are evaluated to assign work to the agent based on capacity. | Tokyo |
| FSM: Onboarding external contractor agent as additional manager for the external assignment group | Verify that when onboarding an external agent for the contractor company, you can assign the additional manager role to the agent. | Tokyo |
| FSM: Dispatcher Workspace - Assign crews to work order tasks that require a group of agents to work on them | - Verify that a dispatcher with the crew moderator role can create a crew in the Dispatcher Workspace. - Verify that a dispatcher with the crew moderator role can assign a work order task to the planned crew in the Dispatcher Workspace | Tokyo |
| FSM: Work order task supports Multi-day task scheduling | Verify the Multiday task scheduling functionality:- Create Work order, work order task, and agent schedule records. - Select the Assign across schedule entries option in the work order task. - Assign an agent to the work order task for which the task duration is more than a day. - Verify that work order task is assigned successfully to the agent and the estimated end time is populated correctly. | Tokyo |
| Verify creating a work order from a case and assigning a work order task to an agent from CSM/ FSM Configurable Workspace | - Verify you can create a work order from a case. - Qualify the work order and verify a work order task is created. - Assign the work order task to an agent and verify the agent it is assigned to is updated correctly. | Xanadu |
| FSM: Appointment Booking unified UI modal validation in platform | - Create work order and work order task. - Launch Seismic Appointment Booking calender in Platform. - Verify that **Today** and **Next week** options displays the correct calender. | Yokohama |
| Create and qualify a work order, then assign the work order from Dispatcher Workspace as a dispatcher | - As a dispatcher, from the CSM/FSM Configurable workspace go to the **List** view and create a new work order. - Then as an administrator, qualify the work order and verify if a work order task is created. - Then as a dispatcher, assign the work order task to a Field Service agent and verify the Assigned to field is update correctly. | Yokohama |
| Clone a work order task | - From from the CSM/FSM Configurable workspace, open any work order task record page. - Select **Clone Work order task**, and verify that a new work order task is created with all details populated from the original work order task. | Yokohama |
| Create a time worked entry as a dispatcher or qualifier | - From the CSM/FSM Configurable workspace, go to the List view and create a new work order. - Qualify the work order and verify that a work order task is created. - Select **Record Time**, then fill in the time worked entry and select **Save**. - Verify that the time worked entry is created successfully. | Australia |
| Flag a work order task from CSM/FSM Configurable workspace | - From the CSM/FSM Configurable workspace, as a user with the Dispatcher or Qualifier role, go to the List view and create a new work order. - Qualify the Work order and verify if a Work order task is created. - Go to the Work order task you created and select **Flag**. Verify the work order task is flagged and you see a **Unflag** button. - Select **Unflag** and verify work order task is now unflagged, and the **Flag** button is available. | Australia |
| Test | Description | Release version |
|---|---|---|
| GRC: Create Audit Engagement and Generate Audit Task | Validates audit engagement creation and associates entities to generate controls and test plans. Generates audit task which is associated to a test plan. | Paris |
| GRC: Create and process a milestone | Create a milestone in an engagement. The due date cannot be in the past and the completion date cannot be in the future. For a milestone in open state, the percent complete is 0 and changes when the milestone state changes. | Paris |
| GRC: Cost and Resource plan rollup | Create an audit plan and associate an engagement to it. Add a cost plan and resource plan to this engagement. Notice that these costs are rolled up to the plan. Any edits to these costs in the engagement are reflected in the plan. | Paris |
| GRC: Create Engagement Project Manual and automatic | On an engagement in the validate state, perform the Enable advanced planning ui-action. Notice that an engagement project gets created. When the state of an engagement associated to an audit plan having "Advanced planning capabilities" is changed to validate, an engagement project gets created automatically. | Paris |
| GRC: Auditable Unit with Detailed Risk Assessment | Create an Auditable unit with method as "Detailed Risk Assessment." Request for Assessing the Risk Assessment by adding the Assessor. After the assessor responds and marks Assessment as Complete, the risk assessment fields are automatically updated. | Paris |
| Test | Description | Release version |
|---|---|---|
| GRC: System Owner create and validate responsibilities and roles for an AB and AP | System Owner creates and validates responsibilities and roles for an Authorization Boundary and Authorization Package.Information Owners and System User are pre-populated when selecting the Authorization Boundary. | Quebec \(compatible with Paris and Orlando\) |
| GRC: System Owner validate App Modules visibility | Verifies that the system owner persona is able to view the Continuous Authorization & Monitoring application menu and the following modules under that menu:- All Authorization Boundaries - All Authorization Packages - Information Type Library - Control Overlays - Control Objectives - Controls - All Engagements | Quebec \(compatible with Paris and Orlando\) |
| GRC: System Owner Request First approval & My approvals module | System Owner requests an approval. | Quebec \(compatible with Paris and Orlando\) |
| SO: Create and validate responsibilities and roles for an AB and AP | Verifies if a system owner can create an Authorization Boundary by completing the fields on the Authorization Boundary form. Also verify if the same SO can create an Authorization Package from the form view. | Quebec \(compatible with Paris and Orlando\) |
| Test | Description | Release version |
|---|---|---|
| HAM - Hardware Normalization | Validates the various normalization status values based on the normalized Manufacturer, Product, and Model. | Orlando |
| HAM - Hardware Asset Disposal work flow | Validates asset disposal work flow. | Paris |
| HAM - Automating Asset deploy workflow | Validates asset deployment work flow. | Paris |
| HAM - Automating Asset Swap workflow | Validates Asset Exchange/Swap work flow.**Note:** Requires demo data. | Paris |
| HAM - Standard Hardware Asset Request Flow | Validates the Standard Hardware Asset Request flow, which is a part of the Hardware Asset Management application. | Paris |
| HAM - Hardware Asset Refresh flow | Validates asset refresh workflow. | Quebec |
| HAM - Loaner Asset Allocation Flow | Validates loaner asset workflow. | Quebec |
| HAM - Lease Contract Asset Expiration | Validates leased contract asset expiration end to end workflow, performing return or extend of the assets covered in the lease contract. | Quebec |
| HAM - Asset RMA Flow | Validates the asset Return Merchandise Authorisation \(RMA\) workflow with Inventory User. | Rome |
| HAM - Asset RMA Flow \(SP\) | Validates the asset Return Merchandise Authorisation \(RMA\) workflow from Service Portal. | Rome |
| HAM - Loaner Asset Request Flow | Validates the Loaner asset allocation workflow with Inventory Admin user. | Rome |
| HAM - Contract Renewal Flow | Validates the Contract Renewal flow with Contract Manager user. | Tokyo |
| Test | Description | Release version |
|---|---|---|
| Case Creation Configuration | Validates an HR service has a case creation configuration and is populated into the HR case form when creating an HR case for that HR service. | Yokohama |
| Create Document template block and block content | Verifies a document template block and document template content are created for block content. | Yokohama |
| Create HR Employee Document | Creates an employee document and ensures the Attachment \[sys\_attachment\] table points back to the record in the Employee Document \[sn\_hr\_ef\_employee\_document\] table.Verifies that the employee document is accessible from the Employee Center or Employee Center Pro via the employee HR profile. | |
| Create Employee Document with Active Document Type | Validates the creation of:- One active document type - One inactive document type - Employee file with active document type **Note:** Human Resources Scoped App: Core \(com.sn\_hr\_core\) and Employee Document Management \(com.sn\_employee\_document\_management\) must be activated. | Yokohama |
| \[Delegation\] Admin - Adding a delegation rule with delegator and delegate user criteria | Verifies that user criteria for a delegation rule works correctly, | San Diego |
| E2E test for Bulk Case Creation | Verifies that bulk cases can be created for selected users in a specific user segment. | San Diego |
| ER: Case Restriction | Verifies that restricted cases are only viewable by users with the sn\_hr\_er.confidential role. | San Diego |
| HR: Case updates visible to employees | Cases created and updated by an HR agent are visible to the Opened for or Subject person | Quebec |
| HR: Creation of 401k enrollment case from portal | Creates a 401\(k\) enrollment case from the Employee Center or Employee Center Pro. Verifies that the case creates successfully. | Madrid |
| HR: Creation of Employee Relations case from ESC portal | Creates a Disciplinary Issue case from the Employee Center or Employee Center Pro. Verifies that the case creates successfully. | New York |
| HR: Creation of Employment Verification Letter case from ESC portal | Creates an Employment Verification Letter case from the Employee Center or Employee Center Pro. Verifies that the case creates successfully. | Madrid |
| HR: Creation of Payroll case from ESC portal | Creates a direct deposit payroll setup case from the Employee Center or Employee Center Pro.Verifies that the case creates successfully. | New York |
| HR: Creation of Tuition Reimbursement request from portal | Creates a Tuition Reimbursement Request case from the Employee Center or Employee Center Pro. Verifies that the case creates successfully. | Madrid |
| HR: Fulfillment Instructions | Verifies that fulfillment instructions are created for a specific condition for an opened for user. Also verifies the fulfillment instructions change when the details of the case changes. | Orlando |
| HR: Fulfillment Instructions conditions for COE specific fields | Verifies the conditions for COE specific fulfillment instruction.Fulfillment instructions update on an HR case based on the conditions defined in the fulfillment instructions. | Quebec |
| HR: General Benefits Inquiry Case Creation | Creates a General Benefits case using the native UI.It also verifies that the case opens and can be updated after case creation. | Madrid |
| HR: Payroll Discrepancy Case Creation | Creates a Payroll Discrepancy case using the native UI.It also verifies that the case opens and can be updated after case creation. | Madrid |
| HR: Reclassify Case Transfer | Tests when an HR case transfers from one COE \(HR service\) to a different COE using the reclassify \(HR case number remains the same\) method. | Orlando |
| HR: Response Template Configuration | Creates a response template for a payroll case and pastes the response in the worknotes. | Quebec |
| HR: Search catalog items & KBs in ESC | Verifies the search functionality in the Employee Center or Employee Center Pro. | Orlando |
| HR: Standard Case Transfer | Tests an HR case transfers from one COE \(HR service\) to a different COE using the standard \(creates HR case number and deletes old number\) case transfer. | Orlando |
| HR: Suspend Case Flow | Tests the ability to suspend an HR case and later resume the case. | Rome |
| HR: Tuition Reimbursement Case Creation | Creates a Tuition Reimbursement HR case. | Orlando |
| HR: Workforce Administration Case Creation | Creates a Workforce Administration case, signs an employee verification letter, and generates the letter. | Orlando |
| JA: Publish & edit plan details | Verifies the ability to delete an existing to-do in an action plan. | San Diego |
| Journey Designer: Create stage and edit stage | Verifies that the user can create a new stage, add a task template to the stage, edit the stage name, and delete the stage. | Vancouver |
| Journey Designer: Add task templates from scratch and edit | Verifies that the user can add a task template using the Build from scratch option, then edit the task template. | Vancouver |
| Journey Designer: Add existing task templates and remove task template | Verifies that a task template can be added to a Journey template with the Use template option, and then removed. | Vancouver |
| Learning Core Task Assignment | Verifies a learning task from a learning catalog can be assigned to a user. | San Diego |
| Test | Description | Release version |
|---|---|---|
| Validation of top-down funding and unfunding | - Validate that the correct amount is allocated from top investment to child investments while funding. - Validate that the correct amount is returned back to the top investment from the child investment while unfunding. | Orlando |
| Validation of bottom-up funding | - Validate that the correct amount is requested by the child investment from the parent investment. - Validate that the correct amount is allocated back to the child investment from the parent investment. | Paris |
| Test | Description | Release version |
|---|---|---|
| KM : Create KCS Template Article with Approval Publish workflow | Verify the creation of a KCS template article with approval publish workflow.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Madrid |
| KM: Create MultiVersioned standard Article with approval publish workflow | Verify the creation of a multi-versioned standard article with approval publish workflow.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Madrid |
| KM: Article level subscription | Verify that users can subscribe to a knowledge article.**Note:** Requires the Knowledge Management Advanced Installer plugin. | New York |
| KM: User criteria covering canRead and canContribute for KnowledgeBase and canRead at Article level | Verify the creation of canRead and canContribute user criteria for knowledge base and canRead user criteria for article.**Note:** Requires the Knowledge Management Core plugin. | Madrid |
| KM: Create a KCS article from a case | Verify the creation of a KCS article from a case.**Note:** Requires the Knowledge Management Advanced Installer and Customer Service Management Demo Data plugins. | Madrid |
| KM: Knowledge Base Level Subscriptions | Verify that users can subscribe to a Knowledge Base.**Note:** Requires the Knowledge Management Advanced Installer plugin. | New York |
| KM: AQI | Verify the creation, assignment, and review of an AQI checklist.**Note:** Requires the Knowledge Management Advanced Installer plugin. | New York |
| KM: Requestor performs search, view the article, provide feedback \(Helpful No with Feedback Task\) | Verify the search request, review, provision of feedback as not helpful, and creation of a feedback task for an article on the Knowledge Management Service Portal.**Note:** Requires the Knowledge Management Advanced Installer plugin. | New York |
| KM: Create and edit an article from Feedback Task form | Confirm the availability of the **Create Article** and **Edit Article** buttons on a Knowledge Feedback Task form.**Note:** Requires the Knowledge Management Advanced Installer plugin. | New York |
| KM: Search for pinned articles and checking the highest click rank | Verify the search request and that the click rank value of a pinned article was added to the Knowledge Searches \(ts\_query\_kb\) table.**Note:** Requires the Knowledge Management Advanced Installer plugin. | New York |
| KM: Create an Ownership Group and check edit permissions and subscriptions | Verify the assignment of an article to an ownership group, that all members of the ownership group are subscribed to the article, and have permission to edit.**Note:** Requires the Knowledge Management Advanced Installer plugin. | New York |
| KM: Create, search for, and view knowledge articles with knowledge blocks | Verify the creation of a knowledge block and its addition to a knowledge article. Also, verify that the knowledge block content is searchable.**Note:** Requires the Knowledge Blocks plugin. | Orlando |
| KM: Validate the Knowledge - Approval Retire workflow | Verify the success of Knowledge - Approval Retire workflow by retiring a published knowledge article.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Orlando |
| KM: Validate feedback task assignment to the ownership group manager | Verify the assignment of a feedback task to the ownership group manager of a knowledge article.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Orlando |
| KM: Validate that the article template selector includes knowledge bases and article templates | Verify that the article template selector includes all knowledge bases with contribute access and article templates applicable to each knowledge base.**Note:** Requires Knowledge Management Advanced Installer. | Orlando |
| KM: Validate the Knowledge - Approval Publish workflow | Verify the success of a Knowledge - Approval Publish workflow by recalling, rejecting, and then approving a knowledge article through the approval process.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Orlando |
| KM: Make an outdated version of an article the latest version | Verify that an outdated version of a knowledge article is made the latest version.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Orlando |
| KM: Validate that the mapped related articles appear in the Related articles widget | Verify that the related articles mapped to a knowledge article appear in the Related articles widget on the knowledge article view page.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Orlando |
| KM: Validate that the mapped related catalog items appear in the Related items widget | Verify that the related catalog items mapped to a knowledge article appear in the Related items widget on the knowledge article view page.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Orlando |
| KM: Validate that a versioned article is created, published, checked out, and retired | Verify the success of UI actions on a versioned knowledge article by creating, publishing, updating, and retiring the knowledge article in Agent Workspace.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Quebec |
| KM: Verify the scheduled publish feature for knowledge articles | Verify the scheduled publish feature for knowledge articles by creating an article in approval publish workflow, putting it for scheduled for publish and observing the change in workflow state from the**Scheduled for publish** state to the **Published** state.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Quebec |
| KM: Validate the Knowledge - Approval Publish workflow in Agent Workspace | Verify the success of a Knowledge - Approval Publish workflow by recalling and then approving a knowledge article through the approval process in Agent Workspace.**Note:** Requires the Knowledge Management Advanced Installer plugin. | Quebec |
| Test | Description | Release version |
|---|---|---|
| \[Leader hub\] - Validate LH flows | - Verifies that the following widgets are present on the At a glance page for user Maria Davies: - Org talent - Skill growth area - Growth engagement - Verifies the employee card for the leader who has accessed Leader Hub appears at the top of the organizational chart on the Org talent page. - Verifies that selecting the **View team details** button on a card for an employee navigates the leader to the Team details page. - Verifies that the Skills widget is present on the Org Skills page. **Note:** Requires demo data. | Xanadu |
| Test | Description | Release version |
|---|---|---|
| OI: Health Metrics Collection | An individual test that verifies the following: - There is at least one Metric Intelligence Metrics extension that is running. - There are entries for the ‘Health Metrics’ in the Metric to CI table. - For each of the Metric Intelligence Metrics extensions that are currently running, that there is data stored in MetricBase. If the test initially fails, wait until the Metric Intelligence Metrics extension runs for at least 10-15 minutes. Then try again. | Madrid |
| Test | Description | Release version |
|---|---|---|
| PRB MGMT: Cancel a Problem when the state of the Problem is Assess | Verify that when a Problem in the **Assess** state is canceled, the state of the Problem changes to **Closed** with **Resolution code** as **Canceled**. | Madrid |
| PRB MGMT: Cancel a Problem when the state of the Problem is Root Cause Analysis | Verify that when a Problem is in the **Root Cause Analysis** state and is canceled, the state of the Problem changes to **Closed** with **Resolution code** as **Canceled**. | Madrid |
| PRB MGMT: Mark a Problem as Duplicate when the state of the Problem is Assess | Verify that when a Problem is in the **Assess** state and is marked as duplicate, the state of the Problem changes to **Closed** with **Resolution code** as **Duplicate**. | Madrid |
| PRB MGMT: Mark a Problem as Duplicate when the state of the Problem is Root Cause analysis | Verify that when a Problem is in the **Root Cause Analysis** state and is marked as duplicate, the state of the Problem changes to **Closed** with **Resolution code** as **Duplicate**. | Madrid |
| PRB MGMT: Accept Risk of Problem \(problem.acceptrisk.move\_to\_closed:false,state:Fix in Progress\) | Verify that when a Problem state is **Fix in Progress** and the risk is accepted, then the Problem state changes to **Resolved** with **Resolution code** as **Risk Accepted**. **Note:** The test is valid when Problem property **Accept Risk moves the Problem to Closed state instead of Resolved state** **\(problem.acceptrisk.move\_to\_closed\)** is false. | Madrid |
| PRB MGMT: Accept Risk of Problem \(problem.acceptrisk.move\_to\_closed:true,state:Fix in Progress\) | Verify that when a Problem state is **Fix in Progress** and the risk is accepted, then the Problem state changes to **Closed** with **Resolution code** as **Risk Accepted**. **Note:** The test is valid when Problem property **Accept Risk moves the Problem to Closed state instead of Resolved state** **\(problem.acceptrisk.move\_to\_closed\)** is true. | Madrid |
| PRB MGMT: Accept Risk of Problem \(problem.acceptrisk.move\_to\_closed:false,state:Root Cause Analysis\) | Verify that when a Problem state is **Root Cause Analysis** and the risk is accepted, then the Problem state changes to **Resolved** with **Resolution code** as **Risk Accepted**. **Note:** The test is valid when Problem property **Accept Risk moves the Problem to Closed state instead of Resolved state** **\(problem.acceptrisk.move\_to\_closed\)** is false. | Madrid |
| PRB MGMT: Accept Risk of Problem\(problem.acceptrisk.move\_to\_closed:true,state:Root Cause Analysis\) | Verify that when a Problem state is **Root Cause Analysis** and the risk is accepted, then the Problem state changes to **Closed** with **Resolution code** as **Risk Accepted**. **Note:** The test is valid when Problem property **Accept Risk moves the Problem to Closed state instead of Resolved state** **\(problem.acceptrisk.move\_to\_closed\)** is true. | Madrid |
| PRB MGMT: Reanalyze Problem which is closed-Risk Accepted from state Root Cause Analysis | Verify that when a Problem is reanalyzed after it is **Closed** with the **Resolution code** as **Risk Accepted**, Problem state changes to **Root Cause Analysis**. | Madrid |
| PRB MGMT: Create Emergency Change from Problem | Verify the creation of Emergency Change from a Problem. | Madrid |
| PRB MGMT: Create Normal Change from Problem | Verify the creation of Normal Change from a Problem. | Madrid |
| PRB MGMT: Problem State Management | Verify problem state management. | Madrid |
| PRB MGMT: Reanalyze a Problem from Complete | Verify that when a Problem is reanalyzed after it is **Closed** with the **Resolution code** as **Fix Applied**, Problem state changes to **Root Cause Analysis**. | Madrid |
| PRB MGMT: Reanalyze a Problem which is canceled from state Assess | Verify that when a Problem is reanalyzed after it is **Closed** with the **Resolution code** as **Canceled**, Problem state changes to **Root Cause Analysis**. | Madrid |
| PRB MGMT: Reanalyze a Problem which is canceled from state Root Cause Analysis | Verify that when a Problem is reanalyzed after it is **Closed** with the **Resolution code** as **Canceled**, Problem state changes to **Root Cause Analysis**. | Madrid |
| PRB MGMT: Reanalyze Problem which is closed-Risk Accepted from state Fix in progress | Verify that when a Problem is reanalyzed after it is **Closed** with the **Resolution code** as **Risk Accepted**, Problem state changes to **Root Cause Analysis**. | Madrid |
| PRB MGMT: Create a Known Error article from Problem | Verify creation of Known Error article from a Problem. | Madrid |
| PRB MGMT: Risk Accept reason on Incident | Verify the **Risk Accepted reason** is copied to the Incidents which are awaiting resolution of a Problem. | Madrid |
| PRB MGMT: Communicate Fix | Verify the communicate fix functionality. | Madrid |
| PRB MGMT: Communicate Workaround | Verify the communicate workaround functionality. | Madrid |
| PRB MGMT: Fix information on Incident | Verify that when a Problem is resolved, the state of the Incidents that are awaiting resolution of the Problem changes to **Resolved**. The fix notes of the Problem are copied to the Incidents. | Madrid |
| PRB MGMT: Problem task \(Type:General\) state management | Verify Problem task state management of a general type Problem. | Madrid |
| Test | Description | Release version |
|---|---|---|
| Validate PPM Cycle from Ideation to demand to project closure | Validate the flow of creating an idea, converting the idea to a demand, and then converting the demand to a project.**Note:** This test fails if the PPM Standard Multicurrency \(com.snc.ppm\_multicurrency\) plugin is active. | Madrid |
| Validation of State and Date Rollup for Automatic Project | Validate the date and state rollup from tasks for a project of type Automatic. | Madrid |
| Validation of State and Date rollup for Manual Project | Validate the date and state rollup from tasks for a project of type Manual. | Madrid |
| Validation of project percent complete when all tasks are Closed Incomplete | Validate the project percent complete when all the tasks are closed as Closed Incomplete. | Orlando |
| Validate Project is not 100 percent complete if it has atleast one task as closed incomplete | Validate the project percent complete is not 100% when at least one task is Closed Incomplete or Closed Skipped with task % complete less than 100%. | Orlando |
| Validate waterfall project does not show Agile Planning Board | Validate that the waterfall projects cannot use the following: - Add stories or epics - Add agile phase - Access Agile board from the project | Orlando |
| Validate dates are rolled up from existing projects to program | Validate that the start and end dates of the project are rolled up to the program to which the project belongs. | Paris |
| Validate dates are rolled up from new projects to program | Validate that the start and end dates of a new project are rolled up to the program to which the project belongs. | Paris |
| Add projects and demands with risks or issues to program | Validate that the projects and demands with risks or issue records associated with them are added to the program. | Paris |
| Add projects and demands with benefit plans to program | Validate that the projects and demands with benefit plans associated with them are added to the program. | Paris |
| Add projects and demands with cost plans to program | Validate that the projects and demands with cost plans associated with them are added to the program. | Paris |
| Validate program dates on addition of existing demands | Validate that the start and end date of the program are adjusted on addition of an existing demand. | Paris |
| Validate program dates on addition of new demands | Validate that the start and end date of the program are adjusted on addition of a new demand. | Paris |
| Validate program state rollup | Validate that the program state is rolled up from state of all the projects in the program. | Paris |
| Verify Demand task due date column field value empty | Validate that the **Due date** field is empty for a new demand task. | Rome |
| Verify baseline is created on Project & Demand when demand is converted to project | Validate that a project and demand baseline is created when a demand is converted to a project. | Rome |
| Verify timecard financial appears on Demand when time card submitted against demand task | Validate that the actual cost of the demand is updated when a time card is processed for a demand task. | Rome |
| Validate demand approved date | Validate that the approved dates for demand and the project created from the demand are the same. | Tokyo |
| Validate project preference "close project milestone tasks when they change to work state" | Validate that milestone tasks are closed when their state is changed to Work in Progress. This test uses the project preference "close project milestone tasks when they change to work state". | Tokyo |
| Validate project preference "Enable move project for WIP projects" | Validate that the project start date changes appropriately for a project in WIP state. This test uses the project preference "Enable move project for WIP projects". | Tokyo |
| Validate project preference "Rollup project start date from tasks" | Validate that the start date of a project task does not roll up to the project. This test deselects the project preference "Rollup project start date from tasks" and verifies behavior when project planned dates differ from the project task start date. | Tokyo |
| Test | Description | Release version |
|---|---|---|
| Validate Planned start date of a project can be shifted by using the Move project action | Validate that the Planned start date can be updated to a later or earlier date using the Move project related link. | Orlando |
| Validate Move Project is disabled when Project is selected for execution | Validate that the Move Project option is not available if the Project is in Execution phase. | Orlando |
| Validate Move Project functionality with sprint dates populated for an agile phase | Validate that the sprint start and end dates are cleared when the project is moved using the Move Project related link.**Note:** This test is available only when Agile Development 2.0 plugin \(com.snc.sdlc.agile.2.0\) is activated. | Orlando |
| Validate Move Project functionality with external dependencies and related entities | Validate that the external dependencies and related entities are also shifted and redrawn when the project is moved using the Move Project related link. | Orlando |
| Validate Move Project functionality with different project states | Validate that the Move Project does not work when the project is in Work In Progress or Closed Complete state. | Orlando |
| Test | Description | Release version |
|---|---|---|
| Verify user resource plan flow from Planned to Canceled state | Validate that the resource plan of a project can be moved to canceled state from planned state. | Madrid |
| Verify group resource plan flow from Planned to Complete state | Validate that the resource plan of a project can be moved to complete state from planned state. | Madrid |
| Verify role resource plan flow from Planned to Allocated state | Validate that the resource plan of a project can be moved to allocated state from planned state. | Madrid |
| Verify aggregated cost of all resource plans roll up to the corresponding project or demand fields | Validate that the aggregated cost of all resource plans on a project or demand roll up to the Planned Cost and Allocated Cost fields. Verify that costs also roll up to the Resource Cost section of respective projects and demands. | Orlando |
| Verify Copy Resource plan option | Validate that the Copy Resource plan option creates an exact copy of the source resource plan in the Planning state | Orlando |
| Verify resource plan aggregate roll up from project/demand to program | Validate that the aggregated cost of all resource plans on a project or demand roll up to the total planned cost of the associated program. | Orlando |
| Verify records on completion of a resource plan | Validate the changes in a resource plan on completion:- The state of the resource plan is updated to Completed. - If the completion date is earlier than the resource plan end date, the end date of the resource plan is updated with the completion date. If the completion date entered is later than the resource plan end date, the resource plan end date is retained. - All the requested and allocation records for the resource plan for the period after the completion date are deleted. If there are any actual hours logged against an allocation, that allocation is not deleted. For those allocation records, the allocated hours become zero and the actual hours are retained. - The available and allocated hours for resources are updated in the aggregate tables. | Orlando |
| Verify records on completion of a resource plan with Planned Duration as allocation type | Validate the following on completion of a resource plan with Planned Duration as allocation type:- The state of the resource plan is updated to Completed. - Allocations are not deleted. - End date of the allocation is updated to the completion date. | Orlando |
| Verify the RP replan Capability | Validate that when a cancelled resource plan is re-planned, the state of the resource plan changes to Planning. | Orlando |
| Verify whether change in resource plan is reflected in corresponding cost plan | Validate that when a resource plan is updated, the corresponding cost plan is updated accordingly. For example, the total planned cost is 500 USD and the planned hours is 10. Changing the planned hours to 20 updates the total planned cost to 1000 USD. | Paris |
| Resource-Test the default population of resource plan start & end date | Validate the following on creating a user or group resource plan from the related list of a demand:- If a demand is created without a start date and end date, the user or group resource plan has task as demand and no start and end date. - If a demand is created with a start date and end date, the user resource plan has the task as demand with those dates. | Paris |
| Validate that actual hours in operational resource plan and time card are equal | Validate that when a time card category is mapped with an operational work type, the actual hours match between the resource plan and time card after submission. | Quebec |
| Verify Resource plan auto population for Operational plans | Validate that the operational resource plans associated with a time card are automatically retrieved on the time card when time is logged. | Rome |
| Verify resource plan auto population for non-operational resource plans | Validate that the resource plans associated with a project, project task, or demand for a time card are automatically retrieved on the time card when time is logged. | Rome |
| Test | Description | Release version |
|---|---|---|
| SAM - Mapping Custom PPN/DMAP to newly published PPN and Content | Validates the replacement of a custom publisher part number \(PPN\) with a new Software Asset Management Content Service PPN. | San Diego |
| SAM - Oracle PaaS BYOL | - Validates the addition of the new Serverless Hardware \[cmdb\_ci\_serverless\_hardware\] table, which stores information about PaaS devices. - Validates the license compliance of Oracle Database in Amazon Web Services \(AWS\) PaaS environments. **Note:** Requires the Software Asset Management Professional for Oracle \(com.snc.samp.oracle\) plugin and the CMDB CI Class Models store application. | Rome |
| SAM - Software Product Lifecycles records on Software Model | Validates that the Software Lifecycle tab on the Software Model form is showing records.**Note:** Requires demo data and the Software Asset Management Professional for Microsoft \(com.snc.samp.microsoft\) plugin. | Quebec |
| SAM - BYOL | - Validates the purchase date on the Software Entitlement form - Validates the addition of newly added column legacy\_license on the License Metric Results \[samp\_license\_metric\_result\] and License Position Report \[samp\_license\_position\_report\] tables - Validates the addition of newly added columns, cloud\_license\_type and cloud\_license \_type\_source in the Software Installations \[cmdb\_sam\_sw\_install\] table **Note:** Requires the Software Asset Management Professional for Micorosft \(com.snc.samp.microsoft\) plugin. | Quebec |
| SAM - Validate CIS Suites | Validates reconciliation of Core Infrastructure Server \(CIS\) suites along with downgrade rights.**Note:** Requires demo data and the Software Asset Management Professional for Microsoft \(com.snc.samp.microsoft\) plugin. | Paris |
| SAM - PerCoreForMSCluster | Verifies the reconciliation functionality for Microsoft per core with cluster.**Note:** Requires the Software Asset Management Professional for Microsoft \(com.snc.samp.microsoft\) plugin. | Paris |
| SAM - Validate upgrade/downgrade during Reconciliation for Microsoft publisher | Validates upgrade and downgrade rights during reconciliation for Microsoft products.**Note:** Requires demo data and the Software Asset Management Professional for Microsoft \(com.snc.samp.microsoft\) plugin. | Paris |
| SAM - Generate demand to consolidate SaaS applications | Validates generation and submission of a demand on SaaS applications.**Note:** Requires the Software Asset Management - Spend Detection \(com.sn\_sam\_spend\) plugin and the PPM standard \(com.snc.financial\_planning\_pmo\) plugin. | Paris |
| SAM - Software Model and Software Entitlement checks for SAP Engines | Verifies that the Software Model and Software Entitlement forms change when the product is an SAP engine.**Note:** Requires the Software Asset Management Professional for SAP \(com.sn\_samp\_sap\) plugin. | Paris |
| SAM - Downgrade Rights on Software Model | Validates that the downgrade rights pushed from the content service are correctly populated on the Downgrade Rights related list on the software model form. | Orlando |
| SAM - Multi-core pack validation on Software Entitlement | Validates the functionality of new fields for a multi-core pack on software entitlements.**Note:** Requires the Software Asset Management Professional for Microsoft \(com.snc.samp.microsoft\) plugin. | Orlando |
| SAM - Downgrade Rights on Software Entitlement | Validates that the downgrade rights pushed from the content service are correctly populated on the Downgrade Rights related list on the software entitlement form. | Orlando |
| SAM - Software Spend Transaction | Validates the creation of a Software Spend Transaction.**Note:** Requires the Software Asset Management - Spend Detection \(com.sn\_sam\_spend\) plugin. | Orlando |
| SAM - Software Model and Software Entitlement | Tests that a user can create a software model and software entitlement and validates those records. | New York |
| SAM - Software Installation and Discovery Model | Tests that a user can create a software installation and discovery model and validates those records. | New York |
| SAM - Software Entitlement Creation Using Custom PPN | Creates a custom software product, a custom DMAP for the custom product, a custom Part Number for the custom DMAP, and a software entitlement using the custom Part Number. Verifies that a software model is automatically created. | New York |
| SAM - Software Model Checks for SAP Named Users | Tests that the software model form changes when the publisher is SAP and the product is Named Users.**Note:** Requires the Software Asset Management Professional for SAP \(com.sn\_samp\_sap\) plugin. | New York |
| SAM - Software Model Checks for SaaS | Tests that the Software Model form changes when a SaaS product is selected.**Note:** Requires the Software Asset Management - SaaS License Management \(sn\_sam\_saas\_int\) plugin. | New York |
| SAM - Validate Fields on SaaS Software Products | Tests that the **Subscription software** and **Ignore installs** fields are present on the Software Product form.**Note:** Requires the Software Asset Management - SaaS License Management \(sn\_sam\_saas\_int\) plugin. | New York |
| Test | Description | Release version |
|---|---|---|
| SIR: Create Security Incident | Determine whether a user can successfully create a security incident from the security incident form. | Madrid |
| SIR: Create Security Incident via Security Incident Catalog | Determine whether a user can successfully create a security incident from the catalog. | Madrid |
| SIR: PIR Assessments OOTB configuration test | Use this test to validate PIR assessments and base system configurations. | Tokyo |
| SIR: PIR Assessments conditional Configuration tests | Verify that security incidents matching the mandatory conditional rule are not closed without completing the post incident assessment. Verify that the security incidents matching the optional conditional rule can be closed without completing the post incident assessment. Verify that assessments are not generated for the security incidents that do not match any rule. | Tokyo |
| SIR: PIR Run Time Experience | Verify that PIR reports are configured and attached to the security incidents as per the new design. | Tokyo |
| SIR: PIR Design Time Experience | Verify that the security incident is mapped with the report template based on the administrator configuration. | Tokyo |
| SIR: Link Security Incident to a existing Major Security Incident | Link a Security Incident to an existing Major Security Incident and validate data from Security Incident rolled up to Major Security Incident. | Tokyo |
| SIR: Promote Security Incident as Major Security Incident | Promote a Security Incident as Major Security Incident and validate data from Security Incident rolled up to Major Security Incident. | Tokyo |
| SIR: Propose Security Incident as Major Security Incident | Propose a Security Incident as Major Security Incident and validate data from Security Incident rolled up to Major Security Incident. | Tokyo |
| SIR: Security Incident life cycle | Validate a Security Incident life cycle with the policy violation response tasks workflow. | Yokohama |
| SIR: Create Security Case | Create a Security Case from the Security Incident form. | Yokohama |
| Verify that only Allowed Members can access the security incident once Enforce Restriction is ON | Verify that only the allowed members can access the security incident once the Enforce Restriction is enabled. | Yokohama |
| Verify that security incident enabled with "Enforce Restriction" is not visible for any user | Verify that security incident enabled with "Enforce Restriction" is not visible for any user. | Yokohama |
| Validate Read Access | Validate the view access. | Yokohama |
| Validate Write Access | Validate the edit access. | Yokohama |
| SIR Workspace: Read Access | Verify that Read Access user can view the security incident without having security roles even on workspace. | Yokohama |
| SIR Workspace: Write Access | Verify that Write Access user can update the security incident without having security roles. | Yokohama |
| SIR Workspace: Create new Security Incident | Create new security incident from workspace. | Yokohama |
| SIR Workspace: Create Response Task | Create new response task from an existing security incident. | Yokohama |
| Now Assist for Security: Active Security Incident Summarization | Summarize an active security incident and validate the displayed sections. | Zurich |
| Now Assist for Security: Security Incident Summarization\_Share to worknotes | Share the generated summary to worknotes. | Zurich |
| Now Assist for Security: Closed Security Incident Summarization | Summarize a closed security incident and validate the displayed sections. | Zurich |
| Test | Description | Release version |
|---|---|---|
| SM OOTB: Tests SM application visibility by roles | Validate the visibility of Service Mapping applications and modules for different roles. For example, the test verifies that a user logged in with the service\_mapping\_user role cannot access the Administration module under Service Mapping. | Madrid |
| SM OOTB: Service map verification | Use this test template to create custom tests for verifying that the topology of the most significant services is unchanged. Configure values under Test Run Data Sets, to identify the name of the service to test and the nodes that you expect to find in this service. For the node name values, enter the node attribute exactly as it appears on the map, for example, "Apache server." If the attribute name for a node is truncated or shows that a node is a CI cluster, configure this node name value to reflect the way it appears on the map, for example, "11x ExchangeF" for a group of 11 Exchange FrontEnd servers. **Note:** You cannot use this test to verify the service content beyond the top, unexpanded level. | Orlando, updated Paris |
| SM OOTB: Check UI accessibility after an upgrade | Run this test to check that the Service Mapping UI is fully functional after an upgrade. | Orlando |
| Test | Description | Release version |
|---|---|---|
| Portfolio Editor: Not Portfolio Owner, Read Only Taxonomy Access | Ensure a portfolio editor can only read associated non-owned portfolio taxonomies. | Orlando |
| Portfolio Editor: Cannot create new Portfolios | Ensure a portfolio editor cannot create new portfolios. | Orlando |
| Portfolio Editor: Valid Portfolio Owner Taxonomy Access | Ensure a portfolio owner has access to taxonomies within owned portfolios. | Orlando |
| Service Editor: Access | Ensure a service editor can only edit owned services and offerings. | Orlando |
| Portfolio Editor: Can Modify Owned Portfolios | Ensure a portfolio editor can modify and update owned portfolios. | Orlando |
| Create a Portfolio | Ensure a portfolio admin can create a new portfolio. | Orlando |
| Portfolio Editor: Cannot Modify Non-Owned Portfolios | Ensure a portfolio editor cannot modify non-owned portfolios. | Orlando |
| Service Workflow | Verify that a service cannot move forward to Catalog phase without a service portfolio, taxonomy node, and service offering attached to it. Verify a service cannot move backward from the Catalog phase to the Pipeline phase. | Orlando |
| Service Portfolio \(Normal\) | Create a service portfolio, taxonomy layer, and taxonomy nodes. | Orlando |
| Create a Portfolio + 3 Taxonomy Layers | Create a service portfolio with three taxonomy layers. | Orlando |
| Service Portfolio \(Exception\) - Taxonomy Layer Definition Set 01 | Create a service portfolio, taxonomy layer, and taxonomy nodes. | Orlando |
| SPM: Create a Portfolio | Create a service portfolio. | Paris |
| SPM: Create a Portfolio + 3 Taxonomy Layers | Create a service portfolio, with three taxonomy layers. | Paris |
| SPM: Service Portfolio \(Normal\) | Create a service portfolio, taxonomy layer, and taxonomy nodes. | Paris |
| SPM: Service Portfolio \(Exception\) - Taxonomy Layer Definition Set 01 | Create a service portfolio, taxonomy layer, and taxonomy nodes. | Paris |
| SPM: Portfolio Editor: Can Modify Owned Portfolios | Ensure a portfolio editor can modify portfolios that they own. | Paris |
| SPM: Portfolio Editor: Cannot Modify Non-Owned Portfolios | Ensure a portfolio editor cannot modify portfolios that they do not own. | Paris |
| SPM: Portfolio Editor: Cannot create new Portfolios | Ensure a portfolio editor cannot create new Portfolios. | Paris |
| SPM: Portfolio Editor: Valid Portfolio Owner Taxonomy Access | Ensure portfolio owners have access to taxonomies that they own. | Paris |
| SPM: Portfolio Editor: Not Portfolio Owner, Read Only Taxonomy Access | Ensure a portfolio editor can only read the taxonomies of portfolios they do not own. | Paris |
| SPM: Service Editor: Access | Ensure a service editor can only edit services and offerings that they own or are a delegate of. | Paris |
| SPM: Service Viewer: Access | Ensure a service viewer has access to view services. | Paris |
| SPM: Service Workflow | Verify a service cannot move forward to Catalog phase without a service portfolio, taxonomy node, and service offering attached to it. Verify a service cannot move backward from Catalog to Pipeline phase. | Paris |
| Test | Description | Release version |
|---|---|---|
| UR: Transferring an HR case to an Incident | Validate if an HR case is transferred to an incident and an incident is created. | Quebec |
| UR: Restrict or Unrestrict universal request | Validates the following:- The fields are restricted and hidden when a routing agent restricts a UR. - Only agents with **sensitiveinfo\_agent** role are allowed to unrestrict the request. - And, after the request is unrestricted all fields are visible. - sys-audit log access is available for agents. | Yokohama |
| UR: Universal Request creation with RITM | Verifies a catalog request for any item from self-service can be created when Universal Request Certified is enabled. | San Diego |