Available quick start tests by application or feature
Validate that your instance still works after you make any configuration change such as apply an upgrade or develop an application. Copy and customize the ServiceNow -provided quick start tests to pass when using your instance-specific data.
Danger
By default, the system property that is used to run automated tests is turned off to prevent you from accidentally running these tests on a production system. To avoid data corruption or an outage, run tests only on development, test, and other non-production instances. See Enable or disable executing Automated Test Framework tests.
Agile Development 2.0
Agile Development 2.0 quick start tests require activating the Agile Development 2.0 plugin (com.snc.sdlc.agile.2.0) and the Agile Development 2.0 - ATF Tests plugin (com.snc.sdlc.agile.2.0.atf ).
| 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 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. | 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. | Quebec |
To learn more about Agile Development 2.0, see Agile Development 2.0.
Enterprise Architecture (formerly Application Portfolio Management)
Enterprise Architecture quick start tests require enabling the Enterprise Architecture – ATF Tests plugin (com.snc.apm.atf).
| Test | Description | Release version |
|---|---|---|
| Enterprise Architecture: Create Business Application | Verify the creation of an application category and then the creation of a business application with users having apm_user role. | Madrid |
| Enterprise Architecture: Create Business Capability | Verify the creation of a parent and child business capability and verify its field values. | Madrid |
| Enterprise Architecture: Test relating Business Service, Business Application, and Software Models | Verify the creation of a business application, business service, using the existing software model, and a relationship between them. | Orlando |
| Enterprise Architecture: Test for Indicator Score and Application Score generation | Verify the creation of indicator, scoring profile, and generation of indicator scores and application scores. | Paris |
| Enterprise Architecture: Business Application with Information Object and Data Domain | Verify the creation of business application, information object, and addition of the CRUD operations in relation attributes. | Quebec |
To learn more about Enterprise Architecture (formerly Application Portfolio Management), see Enterprise Architecture .
Assessments and Surveys
Assessments and Surveys quick start tests require activating the Automated Test Framework for Survey plugin (com.glide.automated_testing_impl. Survey).
| Name | Description | Release version |
|---|---|---|
| Survey: Basic Platform Based Test | Create a survey using Platform UI actions. | Madrid |
| Survey: Platform test for Dynamic Validation | Validate a survey dynamically. | Madrid |
| Survey: Clone Action | Clone a survey and validate the records of the original survey and the cloned survey. | New York |
| Survey: Question Bank Flow | Verify the addition of a question bank to a survey. | New York |
| Survey: Survey Creator Work Flow | Survey creator can create a survey and assign to the user who can take the survey and submit it. | New York |
| Assessment: Assign assessment to assessor | Assign an assessment to an assessor and verify that the instance is created for the assessor. | Orlando |
| Assessment: Create assessment as survey creator | Create an assignment as a survey creator. | Orlando |
| Assessment: Scale and Template support | Create, publish, and assign the assessment. Then take the assessment. | Rome |
| Assessment: Basic test flow | Verify the basic flow of an assessment. | Orlando |
To learn more about Assessments and Surveys, see Service administration.
Change Management
Change Management quick start tests require activating the Change Management - ATF Tests plugin (com.snc.change_management.atf).
| Test | Description | Release version |
|---|---|---|
| Emergency Type Change Request workflow | Process an emergency change request from new to closed. | Madrid |
| On Hold for Emergency type Change Request | Validate the approval state of an on-hold emergency change request. | Madrid |
| Copy Change For Emergency type Change Request | Validate the state of a copied emergency change request. | Madrid |
| Reject By Approver for Emergency type | Validate the state of a rejected emergency change request. | Madrid |
| Revert to new for emergency type | Validate the state of an emergency change request after using the Revert to new UI action. | Madrid |
| Convert Emergency to Normal type | Validate the conversion of an emergency change request to a normal change request. | Madrid |
| Cancel Change Request For Emergency Type | Validate the state of a canceled emergency change request. | Madrid |
| Test | Description | Release version |
|---|---|---|
| Normal Type Change Request Workflow | Process a normal change request from new to closed. | Madrid |
| Convert Normal to Emergency type | Validate the conversion of a normal change request to an emergency change request. | Madrid |
| Copy change on Normal Change Request | Validate the state of a copied normal change request. | Madrid |
| On hold for Normal type Change Request | Validate the approval state of an on-hold normal change request. | Madrid |
| State validation when Reject Normal type Change request by Approver. | Validate the state of a rejected normal change request. | Madrid |
| Revert to New Functionality for Normal Type Change Request | Validate the state of a normal change request after using the Revert to new UI action. | Madrid |
| Cancel Change Request For Normal type | Validate the state of a canceled normal change request. | Madrid |
| Test | Description | Release version |
|---|---|---|
| Standard Change Proposal | Determine whether a user can successfully perform standard change proposal creation, approval, and template publishing processes. | Madrid |
| Test | Description | Release version |
|---|---|---|
| Standard Change Request Workflow | Process a standard change request from new to closed. | Madrid |
| Convert Standard to Emergency Change Request | Validate the conversion of a standard change request to an emergency change request. | Madrid |
| Convert Standard to Normal Change Request | Validate the conversion of a standard change request to a normal change request. | Madrid |
| Test | Description | Release version |
|---|---|---|
| Unauthorized change request Workflow | Process a unauthorized change request from new to closed. | Orlando |
| Create Outage of type planned outage from change request | Validate the creation of an outage of type planned outage from a change request. | Orlando |
| Create Outage of type outage from change request | Validate the creation of an outage of type outage from a change request. | Orlando |
| Test | Description | Release version |
|---|---|---|
| Moderate Risk with UI Action Property | Process a moderate risk with UI action property. | Orlando |
| Low Risk with UI Action Property | Process a low risk with UI action property. | Orlando |
| Leave Alone Risk with UI Action Property | Process a leave alone risk with UI action property. | Orlando |
| High Risk with UI Action Property | Process a high risk with UI action property. | Orlando |
| High Risk with Business Rule Property | Process a high risk with Business rule property. | Orlando |
| Moderate Risk with Business Rule property | Process a moderate risk with Business rule property. | Orlando |
| Test | Description | Release version |
|---|---|---|
| Change against Blackout window | Process a change request against a blackout window. | Orlando |
| Check conflicts for CI Already Scheduled | Validate the conflicts for CI already scheduled. | Orlando |
| Change against Conflict Sources | Validate the change request against conflict sources. | Orlando |
| Test | Description | Release version |
|---|---|---|
| Change Schedules Definitions on New | Process the creation of change schedules definitions from New button on Change Schedules landing page. | Orlando |
| Share Panel On Change Schedules Definition | Validate the share panel on change schedules definition. | Orlando |
| Share Change Schedule Definition | Validate the sharing of change schedules definitions. | Orlando |
| Create Standard Change via Service Portal | Create Standard Change from Service Portal | Yokohama |
To learn more about Change Management, see Change Management.
Cloud Provisioning and Governance
Cloud Provisioning and Governance quick start tests require activating the following Cloud Provisioning and Governance plugins:
- Cloud Provisioning and Governance (com.snc.cloud.mgmt)
- Domain Support- Domain Extensions Installer plugin (com.glide.domain.msp_extensions.installer)
- Service Catalog- Domain Separation plugin (glideapp.servicecatalog.domain_separation)
| Test | Description | Release version |
|---|---|---|
| CMP: Add Azure Credentials | Add Azure credentials by inserting the fields into the Credentials table. | Orlando |
| CMP: Azure Service Account | Add Azure service account by inserting the fields into the service account table. | Orlando |
| CMP: Update datacenter type | Update the Cloud Service account with the datacenter type. | Orlando |
| CMP: Creating Resource Group | Creating Resource Group to provision Azure stack via ARM Template. | Orlando |
| CMP: Create Azure Logical datacenter. | Create Azure Logical datacenter for provisioning resources. | Orlando |
| CMP: Create "Contains: Contained by" relationship. | Create "Contains: Contained by" relationship between Resource Group and Azure datacenter. | Orlando |
| CMP: Create 'Hosted on' relationship. | Create hosted on relationship between logical datacenter and Cloud Service account. | Orlando |
| CMP: Create Cloud Account | Create cloud account by inserting the fields into the cloud account table. | Orlando |
| CMP: Cloud account and Logical datacenter association | Create an association between CMP cloud account and Logical datacenter. | Orlando |
| CMP: Create Catalog Item | Create Cloud Catalog Item with ARM Template. | Orlando |
| CMP: Create template version. | Create Cloud Template Version for Cloud Catalog Item. | Orlando |
| CMP: ARM template body | Update Cloud Template Version with ARM template body. | Orlando |
| CMP: Open the 'ServiceNow Cloud Template Versions' | Open the 'ServiceNow Cloud Template Versions' GUI page. | Orlando |
| CMP: Activate Cloud Template Version | Activate Cloud Template Version to create resource block, blueprint, and catalog. | Orlando |
| CMP: Verify the Cloud Template Version. | Validate whether status is Success and state is active in the Cloud Template Version after Activation operation. | Orlando |
| CMP: Activate Cloud Catalog Item | Activate Cloud Catalog Item to display catalog order form to the cloud user. | Orlando |
| CMP: Add stack and resource group name in Catalog item | Set the default value for stack name and resource group in the catalog item. | Orlando |
| CMP: Verify whether stack is present | Validate whether stack is available with name "ATFARMStack". | Orlando |
| CMP: Open Cloud Catalog Item page | Open Cloud Catalog Item page in the Service Portal. | Orlando |
| CMP: Submit Catalog form | Submit the Catalog Form to start provisioning ARM stack. | Orlando |
| CMP: Verify whether stack status is active | Validate the status of a stack after provisioning the stack. | Orlando |
| CMP: Verify stack status after Day2 - Stop operation | Validate the status of the stack status changed from 'On' to 'Off' after the Stop operation. | Orlando |
| CMP: Verify stack status after Day2 - Start operation | Validate the status of the stack status changed from 'Off' to 'On' after the Start operation. | Orlando |
| CMP: Verify stack status after Day2 - Deprovision operation | Validate the status of the stack status changed from 'On' to 'Terminate' after the de-provisioning operation. | Orlando |
| Test | Description | Release version |
|---|---|---|
| CMP: Add AWS Credentials | Add AWS credentials by inserting the fields into the credential table. | Orlando |
| CMP: AWS Service Account | Add AWS service account by inserting the fields into the service account table. | Orlando |
| CMP: Update datacenter type | Update the cloud service account with the datacenter type. | Orlando |
| CMP: Create logical datacenter | Create Logical datacenter for provisioning the resources. | Orlando |
| CMP: Create hosted on relationship | Create hosted on relationship between logical datacenter and Cloud Service account. | Orlando |
| CMP: Create Cloud Account | Create cloud account by inserting the fields into the cloud account table. | Orlando |
| CMP: Cloud account and Logical datacenter association | Create an association between CMP cloud account and logical datacenter. | Orlando |
| CMP: Create Catalog Item | Create Cloud Catalog Item with the CFT Template. | Orlando |
| CMP: Create template version | Created Cloud Template Version for a Cloud Catalog Item. | Orlando |
| CMP: CFT template body | Update Cloud Template Version with the CFT template body. | Orlando |
| CMP: Open the ' ServiceNow Cloud Template Versions' | Open the ' ServiceNow Cloud Template Versions' GUI page. | Orlando |
| CMP: Activate Cloud Template Version | Activate Cloud Template Version to create resource block, blueprint, and catalog. | Orlando |
| CMP: Verify the Cloud Template Version | Validate the Cloud Template Version whether status is Success and state is active after Activation operation. | Orlando |
| CMP: Activate Cloud Catalog Item | Activate Cloud Catalog Item to display the catalog order form to the cloud user. | Orlando |
| CMP: Add stack name in Catalog item | Set the default value for stack name in the catalog item. | Orlando |
| CMP: Verify whether stack is present | Validate whether stack is available with name "ATFCFTStack". | Orlando |
| CMP: Open Cloud Catalog Item page | Open the Cloud Catalog Item page in the Service Portal. | Orlando |
| CMP: Submit Catalog form | Submit the Catalog Form to start provisioning CFT Stack. | Orlando |
| CMP: Verify whether stack status is active | Validate the status of the stack after provisioning the stack. | Orlando |
| CMP: Verify stack status after Day2 - Stop operation | Validate the status of the stack status changed from 'On' to 'Off' after the Stop operation. | Orlando |
| CMP: Verify stack status after Day2 - Start operation | Validate the status of the stack status changed from 'Off' to 'On' after the Start operation. | Orlando |
| CMP: Verify stack status after Day2 - De-provision operation | Validate the status of the stack status changed from 'On' to 'terminate' after the de-provisioning operation. | Orlando |
To learn more about Cloud Provisioning and Governance, see Cloud Provisioning and Governance.
Coaching
Coaching quick start tests requires activation of the Coaching plugin (com.sn_coaching).
| Test | Description | Release version |
|---|---|---|
| Coaching: Create an assessment manually when logged in as a coach. | As a coach, verify that you can create an assessment and assign it to trainees. | Orlando |
| Coaching: Add skills to an opportunity and verify those skills awarded to trainee. | Add skills to a coaching opportunity and verify that those skills have been awarded to trainees after they complete an assessment. | Orlando |
| Coaching: Complete an assessment as a virtual coach. | Verify that the virtual coach completes an assessment and provides feedback to the trainee when a virtual coach is attached to an opportunity. | Orlando |
| Coaching: Add skills to an assessment and verify those skills awarded to trainee. | Add skills to a coaching assessment and verify that those skills have been awarded to trainees after they complete an assessment. | Orlando |
| Coaching: Add skills to a recommendation and verify those skills awarded to trainee. | Add skills to a coaching recommendation and verify that those skills have been awarded to trainees after they complete an assessment. | Orlando |
| Coaching: Move assessments from one state to another when logged in as a coach. | As a coach, verify that you can move an assessment from one state to another. | Orlando |
| Coaching: Attach a recommendation learning to an assessment. | Verify that a recommendation learning on an opportunity gets attached to an assessment when an assessment is generated. | Orlando |
| Coaching: When a coaching opportunity is inactive, assessments are not generated. | Verify that when a coaching opportunity is in inactive state, it does not generate assessments. | Orlando |
| Coaching: Submit Coaching survey as a Coach user. | Verify that coach can submit survey for a trainee. | Quebec |
| Coaching: Submit Coaching survey as a Traineer user. | Verify that trainee can submit survey for a coach. | Quebec |
To learn more about coaching, see Coaching.
Communities
Communities quick start tests require activating the Customer Communities plugin (com.sn_customer_communities) and the Communities Demo Data plugin (com.sn_communities_demo).
| Test | Description | Release version |
|---|---|---|
| Post question and validate feed | Verify that a question is posted in the community and validate whether it appears in the content feed. | Madrid |
| Post video | Verify that a video is posted in the community. | Madrid |
| Forum membership approval | Verify that a membership request to a forum is approved. | Madrid |
| Forum membership reject | Verify that a membership request to a forum is rejected. | Madrid |
| Approve a moderation task | Verify that a moderation task is approved. | Madrid |
| Reject a moderation task | Verify that a moderation task is rejected. | Madrid |
| Topic subscription and activity feed validation | Verify that a topic is subscribed to and the topic activities appear in the activity feed. | New York |
| Approve content approval workflow task on question | Verify the content approval workflow of a question. | New York |
| Question auto-subscription and activity feed validation | Verify that the author is automatically subscribed to the question and the question activities appear in the activity feed. | New York |
| Follow a user | Verify that a community user is able to follow another community user. | New York |
| Reject content approval workflow task on question | Verify the content approval workflow of a question when content is rejected. | New York |
| Gamification on video posting | Verify the gamification points gained when posting a video. | New York |
| Forum subscription and activity feed validation | Verify that a forum is subscribed to and the forum activities appear in the activity feed. | New York |
| Question subscription and activity feed validation | Verify that a question is subscribed to and the question activities appear in the activity feed. | New York |
| Post a video with 'Disable comment' option | Verify a video is posted with Disable comments option as selected. | Orlando |
| Pin a video as Featured | Verify that a video is marked as featured by community administrator in the forum and community home page. | Orlando |
To learn more about Communities, see Communities.
Configuration Compliance
Configuration Compliance quick start tests require activating the Configuration Compliance application (sn_vulc) and loading the demo data.
| Test | Description | Release version |
|---|---|---|
| Configuration Compliance Assignment Rules | Create an assignment rule. | Yokohama |
| Configuration Compliance - Reapply Group Rule | Reapply a test result group rule. | Yokohama |
| Configuration Compliance - Delete Group Rule | Delete a test result group rule. | Yokohama |
To learn more about Configuration Compliance, see Configuration Compliance.
Configuration Management Database (CMDB)
Configuration Management Database (CMDB) quick start tests require activating the Configuration Management (CMDB) plugin (com.snc.cmdb) and the CMDB - ATF Tests plugin (com.snc.cmdb.atf).
| Test | Description | Release version |
|---|---|---|
| CMDB BSM: Dependency Views | Test functionality of Dependency Views APIs. These APIs retrieve Dependency Views map and associated map items such as context menu items, for a given CI sys_id and using sn_cmdb_editor or itil user role. | New York |
| 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 |
|---|---|---|
| CMDB QB: Query Builder - cmdb_query_builder Role | Verify that cmdb_query_builder user role can save queries, and access and run all saved queries, in CMDB Query Builder. | New York |
| CMDB QB: Query Builder - cmdb_query_builder_read Role | Verify that cmdb_query_builder_read user role can access and run all saved queries, and cannot save any query, in CMDB Query Builder. | New York |
| Test | Description | Release version |
|---|---|---|
| CMDB REL EDITOR:Relationship Editor | Check addition of relations to a CI and deletion of relations from a CI using sn_cmdb_editor and itil user roles. | New York |
| CMDB REL FORMATTER:Relationship Formatter | Check accuracy of CI information, relationship types, relationships, associated records such as change tickets, and settings such as CMDB views (relationship filters), displayed for a specific CI in relationship formatter using sn_cmdb_editor and itil user roles. | New York |
| Test | Description | Release version |
|---|---|---|
| CMDB SDK: Query CMDB Metadata | Test querying CMDB metadata. | New York |
| CMDB SDK: Create a relation for a CI using REST APIs | Test creation of a relationship for a CI in the CMDB using the CMDB REST APIs. | New York |
| CMDB SDK: Delete a relation for a CI using REST APIs | Test deletion of a relationship for a CI using CMDB REST APIs. | New York |
| CMDB SDK: Create a CI using REST API | Test creation of a CI using CMDB REST APIs. | New York |
| CMDB SDK: Query CMDB using REST APIs | Test querying the CMDB using CMDB REST APIs. | New York |
| CMDB SDK: Update a CI using REST APIs | Test updating of a CI using CMDB REST APIs. | New York |
| CMDB SDK: Query for a CI using REST APIs | Test querying a CI using CMDB REST APIs. | New York |
To learn more about Configuration Management Database, see Configuration Management Database.
Continual Improvement Management
Continual Improvement Management quick start tests require activating the Continual Improvement Management Automated Tests plugin (com.sn_cim.atf)
| Test | Description | Release version |
|---|---|---|
| CIM: Inbound integration from Assessments | Create an improvement initiative from an assessment. | Paris |
| CIM: Inbound integration from Incident Management | Create an improvement initiative from an incident. | Paris |
| CIM: Inbound integration from Problem Management | Create an improvement initiative from a problem. | Paris |
| CIM: Inbound integration from Survey Management | Create an improvement initiative from a survey. | Paris |
To learn more about Continual Improvement Management, see Continual Improvement Management.
Customer Service Management
All Customer Service Management quick start tests require activating the Customer Service Management Demo Data plugin (com.snc.customerservice.demo). Some quick start tests also require activating the following plugins:
- Business Location (com.snc.business_location)
- Case Playbook for Complaints (sn_complaint)
- Case Playbook for Onboarding (sn_onboarding)
- Consumer Service Portal (com.glide.service-portal.consumer-portal)
- CSM Contributor User (com.snc_csm_contributor_user)
- CSM Extension for Proxy Contacts (com.snc.csm_proxy_contacts)
- Customer Household Data Model (com.snc.household)
- Customer Service Management for Orders (com.snc.csm.order)
- Customer Service Portal (com.glide.service-portal.customer-portal)
- Customer Service with Request Management (com.sn_cs_sm_request)
- Customer Service with Service Management (com.sn_cs_sm)
- Guided Decisions Experience (com.snc.guided_decisions_playbook_experience)
- Guided Decision - Next Best Action (com.snc.next_best_action)
- Major Issue Management (com.sn_majorissue_mgt)
- Proactive Customer Service Operations with Event Management (com.snc.proactive_cs_itom)
- Skill Determination (com.snc.skill_determination)
- UX ATF Action (com.glide.ux.atf_action)
- Walk-Up for CSM (com.snc.walkup_for_csm)
| 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 Workspace: Case creation Workflow | Tests the creation of a case record by a customer service manager in CSM/FSM Configurable Workspace. | Xanadu |
| CSM Workspace: Case follow up workflow | Tests the requesting of information from a customer by a customer service manager in CSM/FSM Configurable Workspace. | Xanadu |
| CSM Workspace: Report knowledge gap workflow | Tests the creation of a knowledge feedback task for a case record by a customer service manager in CSM/FSM Configurable Workspace. | Xanadu |
| CSM Workspace: Case resolution workflow | Tests the resolution of a case record by a customer service manager in CSM/FSM Configurable Workspace. | Xanadu |
| CSM Workspace: Create Incident from Case | Tests the creation of an incident record from a case record by a customer service agent in CSM/FSM Configurable Workspace. | Xanadu |
| CSM Workspace: Create Problem from Case | Tests the creation of a problem record from a case record by a customer service agent in CSM/FSM Configurable Workspace. | Xanadu |
| CSM Workspace: Create Normal Change from Case | Tests the creation of a change record from a case record by a customer service agent in CSM/FSM Configurable Workspace. | Xanadu |
| CSM Workspace: Case creation from All Cases list | Tests the creation of a case from the All cases list by a customer service manager (sn_customerservice_manager) in CSM/FSM Configurable Workspace. | Yokohama |
| CSM Workspace: Case Creation from My Cases list | Tests the creation of a case from the My Cases list by a customer service manager (sn_customerservice_manager) in CSM/FSM Configurable Workspace. | Yokohama |
| CSM Workspace: Case Creation from My Open cases list | Tests the creation of a case from the My Open list by a customer service manager (sn_customerservice_manager) in CSM/FSM Configurable Workspace. | Yokohama |
| CSM Workspace: Interaction creation from My Interaction list | Tests the creation of an interaction record from the My Interactions list by a customer service manager (sn_customerservice_manager) in CSM/FSM Configurable Workspace. | Yokohama |
| Test | Description | Release version |
|---|---|---|
| Create a Complaint Case | Tests that a user can create a case that is of type complaint in the sn_complaint_case table. | Paris |
| Escalate a Complaint Case | Tests that a user can escalate a case that is of type complaint in the sn_complaint_case table. | Paris |
| Test | Description | Release version |
|---|---|---|
| Create an Onboarding Case | Tests that a user can create a case that is of type onboarding in the sn_onboarding_case table. | Paris |
| Escalate an Onboarding Case | Tests that a user can escalate a case that is of type onboarding in the sn_onboarding_case table. | Paris |
| Test | Description | Release version |
|---|---|---|
| awa_admin_operations_dashboard | Verify whether user with role awa_admin is able to view the Advanced Work Assignment menu under Operations Dashboard and unassigned interactions and unassigned task work items modules. | Orlando |
| awa_manager_operations_dashboard | Verify whether user with role awa_manager is able to view the Advanced Work Assignment menu under Operations Dashboard and unassigned interactions and unassigned task work items modules. | Orlando |
| 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 |
|---|---|---|
| Validate Next Best Action List- Guided Decisions | Validates the list of next best actions recommended based on the configured rules. | San Diego |
| Validate Next Best Action Ranking- Guided Decisions | Validates the list of next best actions recommended based on the configured rules. | San Diego |
| Test | Description | Release version |
|---|---|---|
| TC - Create Recipient List | Create a recipient list with the required parameters. Verify the new recipient list in the related list "Recipients". | Orlando |
| TC - Create Publication | Create a publication. The publication is published based on the publication date and verify if an user in the recipient list gets the publication. | Orlando |
| 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 |
|---|---|---|
| CSM PPM: Case creation from project workflow | As a customer service agent, create a case from a CSM project record in CSM Configurable Workspace. | Yokohama |
| CSM PPM: Case creation from project task workflow | As a customer service agent, create a case from a CSM project task record in CSM Configurable Workspace. | Yokohama |
To learn more about Customer Service Management, see Customer Service Management.
Dashboards
Dashboards quick start tests require activating the Automated Test Framework - Responsive Dashboards plugin (com.glide.automated_testing_impl.dashboards). This plugin is active on zBoot of the instance.
| Test | Description | Release version |
|---|---|---|
| Responsive Dashboard Sharing | Confirm dashboard sharing by impersonating users. | Madrid |
| Responsive Dashboard Visibility | Confirm dashboard visibility by impersonating users. | Madrid |
To learn more about Dashboards, see Dashboards.
DevOps
DevOps quick start tests are available when you install the DevOps application from ServiceNow Store.
| Test | Description | Release version |
|---|---|---|
| DevOps Code Tool Flow | Verify the Workflow Studio flow for a DevOps coding tool. | Madrid |
| DevOps Orchestration Flow with CR | Verify the Workflow Studio flow for a DevOps orchestration tool that includes a change request. | Madrid |
| DevOps Orchestration Tool Flow | Verify the Workflow Studio flow for a DevOps orchestration tool. | Madrid |
| DevOps Plan Tool Flow | Verify the Workflow Studio flow for a DevOps planning tool. | Madrid |
To learn more about DevOps, see DevOps Change Velocity.
Employee Center
| 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 |
Essential SAFe
Essential SAFe quick start tests require activating the Agile - Scaled Agile Framework - Essential SAFe plugin (com.snc.sdlc.safe) and the Agile - Scaled Agile Framework - Essential SAFe - ATF Tests plugin (com.snc.sdlc.safe.atf).
| Test | Description | Release version |
|---|---|---|
| Essential SAFe: Feature tests | Verify feature global rank updates. | Madrid |
| Essential SAFe: Feature tests | For a SAFe feature, verify that:
| 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. | 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 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:
| 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. | 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. | 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 only the committed PI objectives, as compared to the PBV of the program in the PI | 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 only the committed PI objectives, as compared to the PBV of the team in the PI | Rome |
To learn more about Essential SAFe, see Essential SAFe.
Event Management
Event Management quick start tests require activating the Event Management plugin (com.glideapp.itom.snac).
| Test | Description | Release version |
|---|---|---|
| EMSelfMonitoring | Track problems with the Event Management plugin after upgrade. To understand the details of issues found, open the All Alerts list and search for alerts that failed, whose source is EMSelfMonitoring, and that were opened or reopened since the upgrade. The exact time for filtering can be found in the error message. | Madrid |
To learn more about Event Management, see Event Management.
Field Service Management
Field Service Management quick start tests are available when you enable the Field Service Management plugin (com.snc.work_management). Enable the demo data plugin (com.snc.work_management.demo) in a non-production instance to start using the quick start tests available with your application. Activate Field Service Contractor Management plugin (com.snc.fsm_contractor_management) to execute the External contractor related tests. You can also modify existing data and customize it to run the quick tests.
| 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 |
| 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 |
| Yokohama |
| Create and qualify a work order, then assign the work order from Dispatcher Workspace as a dispatcher |
| Yokohama |
| Clone a work order task |
| Yokohama |
| Create a time worked entry as a dispatcher or qualifier |
| Australia |
| Flag a work order task from CSM/FSM Configurable workspace |
| Australia |
Finance Close Automation
Finance Close Automation quick start tests are available when you install the Finance Close Automation application from ServiceNow Store.
| Test | Description | Release version |
|---|---|---|
| FCA: Applicable Months sub-set tests | Verify that the Applicable months can only be sub-set of functional workbook. | New York |
| FCA: dates validations | Verify that the date related calculations are correct. | New York |
| FCA: task relationships | Verify that dates and states are updated correctly for the tasks having relationships. | New York |
| FCA: relationship with parent tasks | Verify that dates and states are updated correctly for tasks that have relationship with parent tasks. | New York |
| FCA: Reset Task | Verify the FCA workflow when the task is reset. | New York |
| FCA: Reject Task | Verify the FCA workflow when the task is rejected. | New York |
| FCA: Create JE Task | Verify that ERP source is available for a Journal Entry task type. | New York |
| FCA: Negative values as close day | Verify that both the positive and negative values are acceptable for close day and the planned dates are calculated correctly. | New York |
| FCA: Close day checks for Daily close Checklist | Close day verifications in daily close workbook. | New York |
| FCA: Daily close planned end date checks | Verify planned end dates in a daily close workbook. | New York |
| FCA: Kickstart errors | Verify that all the kickstart validations run. | New York |
| FCA: One final task verification | Verify that there is only one final task in each functional workbook. | New York |
| FCA: Confidential task | Verify that only the owner, reviewer, and approver of a confidential task can view the task. | New York |
| FCA: Unique checklist Verification | Verify that only one workbook is created for a specific day or period. | New York |
| FCA: Milestone and JE Validations | Verify that milestone and journal entry tasks don't have any child tasks. | New York |
Financial Management
Financial Management quick start tests require activating the Financial Management Core - ATF Tests plugin (com.snc.financial_management.atf)
| Test | Description | Release version |
|---|---|---|
| Verify FM Cost Allocation Flow | Verify the cost allocation flow in financial modeling. | Madrid |
Granular Delegation
Granular Delegation quick start tests require activating the Granular Delegation (com.glide.granular_service_delegation) plugin.
| Test | Description | Release version |
|---|---|---|
| [Delegation] Admin - Adding a delegation rule with delegator and delegate user criteria | Ensures a delegate or delegator honors the user criteria assigned to an HR task. | Australia |
GRC Audit Management
GRC: Audit Management quick start tests require activating the GRC: Audit Management plugin (com.sn_audit) and loading the demo data.
| 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, notice that the due date cannot be in past and the completion date cannot be in future and for a milestone in open state the percent complete is 0 which changes in accordance with the milestone state change. | Paris |
| GRC: Cost and Resource plan rollup | Create an audit plan and associate an engagement to it, on adding cost plan and resource plan to this engagement, notice that these costs are rolled up to the plan. Any edits to these costs in engagement reflects in the plan. | Paris |
| GRC: Create Engagement Project Manual and automatic | On an engagement in the validate state, once the Enable advanced planning ui-action is performed notice an engagement project gets created and when the state of an engagement associated to an audit plan having "Advanced planning capabilities" is changed to validate notice that an engagement project gets created automatically. | Paris |
| GRC: Auditable Unit with Detailed Risk Assessment | Create an Auditable unit with method as "Detailed Risk Assessment" and request for Assessing the Risk Assessment by adding the Assessor once the assessor responds and Marks Assessment as Complete after performing the control assessment and residual assessment, the risk assessment fields should be auto updated. | Paris |
To learn more about Audit Management, see Audit Management.
GRC Continuous Authorization and Monitoring
GRC: Continuous Authorization and Monitoring quick start tests require activating the Continuous Authorization and Monitoring plugin (com.sn_compliance) and loading the demo data.
| 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\) |
To learn more about Continuous Authorization and Monitoring, see Continuous Authorization and Monitoring.
GRC Policy and Compliance Management
GRC: Policy and Compliance Management quick start tests require activating the Policy and Compliance Management plugin (com.sn_compliance) and loading the demo data.
| Test | Description | Release version |
|---|---|---|
| GRC: Create Controls | Validates control creation. | Madrid |
| GRC: Create Policy Exception and Flow | Create a policy exception and navigate through its states. | Paris |
| GRC: Policy Lifecycle | Create a policy and navigate through its states. | Paris |
To learn more about Policy and Compliance Management, see Policy and Compliance Management.
GRC Risk Management
GRC: Risk Management quick start tests require activating the Risk Management plugin (com.sn_risk) and loading demo data.
| Test | Description | Release version |
|---|---|---|
| GRC: Create Profile | Validate profile creation. | Madrid |
| GRC: Create Risk | Validates risk creation. | Madrid |
| GRC: Create Control | Validates control creation. | New York |
| GRC: Create Control Objective and Generate Controls | Validates control objective creation and associates profiles to generate controls. | New York |
| GRC: Create Issue | Validates issue creation | New York |
| GRC: Accept an Issue | Validates all the states of an issue till it is closed by accepting the issue. | New York |
| GRC: Remediate an Issue | Validates issue cannot be closed be with an open remediation task. | New York |
| GRC: ATF Flow for Indicator (Manual): | Create an indicator template with type manual and associate a control objective to it. Execute one of the indicators thus formed. Mark the state of the indicator task created as closed and result as failed. The associated control will become non- compliant and an issue will be generated. | New York |
| GRC: ATF flow for Indicator (Basic) | Create an indicator template with type basic and result as failed. Associate a control objective to it and give the supporting data. Execute one of the indicators thus formed. The associated control will become non- compliant and an issue will be generated. | New York |
| GRC: ATF flow for indicator (Script) | Create an indicator template with type script and enter a script and set the value of result.passed and result.value. Associate a control objective to it. Execute one of the indicators. The associated control will become non-compliant and an issue will be generated. | New York |
To learn more about Risk Management, see Risk Management.
Hardware Asset Management
Hardware Asset Management quick start tests are available when you install the Hardware Asset Management (HAM) application from the ServiceNow Store.
| 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 |
To learn more about Hardware Asset Management, see Hardware Asset Management.
HR Service Delivery
| 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 |
Note: Requires plugin activation of:
- Human Resources Scoped App: Core plugin (com.sn_hr_core)
- Employee Service Center [com.sn_hr_service_portal]
| Test | Description | Release version |
|---|---|---|
| Configure HR Service for Auto Case Closure | Verifies that Lifecycle event cases are automatically closed. | Orlando |
| Create Employee request and associate it to LE case | Creates and validates that an employee request appears in the Lifecycle Event case action list. | Rome |
| Create Employee request for old ticket page | Validates if employee requests can be created from the legacy ticket page. | Yokohama |
| [Delegation] Admin - Adding a delegation rule with delegator and delegate user criteria | Verifies user criteria is working for delegation rules for a delegator and delegate user. | Yokohama |
| HR Lifecycle: Access Ticket page for a NewHire Onboarding Case in Employee Service Center | Verifies creation of a new hire and can access the Ticket page of the Employee Service Center. | Orlando |
| HR Lifecycle: Access ESC ticket page and todos page and complete assigned todos | Creates a Tuition Reimbursement Request case from Employee Service Center and the Complete NDA to-do from the subject person. | Orlando |
| HR LifeCycle: Request Onboarding Case Creation | Creates a Request Onboarding case using the native UI and updates the case after creation. | Madrid |
| HR Lifecycle: Trigger Rescind Workflow | Triggers the Rescind workflow for a New Hire Onboarding Lifecycle Event case. | Quebec |
| HR Lifecycle: Verify Requests page for Open and Closed cases | Verifies open and closed cases on the Requests page. | Orlando |
| HR Lifecycle: Verify search in Requests Page | Verifies the search functionality on the Requests page for open and closed cases. | Orlando |
| [LE]: Add Ad hoc task | Verifies an ad hoc task can be added for a Lifecycle Event case. | Yokohama |
Note: Requires plugin activation of:
- Human Resources Scoped App: Core plugin (com.sn_hr_core)
- Human Resources Scoped App: Lifecycle Events [com.sn_hr_lifecycle_events]
- Human Resources Scoped App: Lifecycle Events for Enterprise plugin [com.sn_hr_lifecycle_ent]
- Employee Service Center [com.sn_hr_service_portal]
| Test | Description | Release version |
|---|---|---|
| Create knowledge block and attach block to article | Creates a knowledge block, publishes the block, and attaches the block to a knowledge article. | New York |
| Preview Knowledge Articles with Knowledge Blocks | Tests for preview of knowledge article that contains knowledge blocks. | New York |
Note: Requires plugin activation of Human Resources Scoped App: Core plugin (com.sn_hr_core)
To learn more about HR Service Delivery, see HR Service Delivery.
Incident Management
Incident Management quick start tests require activating the Incident Management - ATF Tests plugin (com.snc.incident.atf).
| Test | Description | Release version |
|---|---|---|
| INCIDENT MGMT: Incident Resolution SLA | Test to verify the Incident Resolution SLA baseline functionality. | Madrid |
| INCIDENT MGMT: Incident Response SLA | Test to verify the Incident Response SLA baseline functionality. | Madrid |
| INCIDENT MGMT: Copy Incident | Test to verify whether the fields from the original Incident are copied correctly to the new Incident. | Madrid |
| INCIDENT MGMT: Copy Incident from a Closed Incident | Test to verify that the Copy Incident UI action is visible for closed Incidents. | Madrid |
| INCIDENT MGMT: Create Standard Change from Incident | Test to verify the creation of a Standard Change from an Incident. | Madrid |
| INCIDENT MGMT: Create of Emergency Change from an Incident | Test to verify the creation of an Emergency Change from an Incident. | Madrid |
| INCIDENT MGMT: Create Normal Change from an Incident | Test to verify the creation of a Normal Change from an Incident. | Madrid |
| INCIDENT MGMT: Create Problem from an Incident | Test to verify the creation of a Problem from an Incident. | Madrid |
| INCIDENT MGMT: Create Knowledge from an Incident | Test to verify the creation of a Knowledge from an Incident. | Madrid |
| INCIDENT MGMT: Incident State flow | Test to verify the state flow of an incident. | Madrid |
| INCIDENT MGMT: Reopening an Incident | Test to verify the reopen incident functionality. | Madrid |
| INCIDENT MGMT: Incident Assignment | Test to verify the incident assignment functionality. | Madrid |
| INCIDENT MGMT: Create child Incident using UI action and verify its fields | Test to verify the creation of a child Incident from an Incident through the Create Child Incident UI action. The test also verifies that the fields of the child Incident get copied correctly from the parent incident to the child incident. | Madrid |
| INCIDENT MGMT: Incident creation — Self Service | Test to verify the creation of an Incident using the Create Incident catalog item. | Madrid |
| INCIDENT MGMT: Parent and Child Incident state sync up | Test to verify that the state of a child Incident synchronizes with the parent Incident when the child Incident is created. | Madrid |
| INCIDENT MGMT: Parent and child Incident state sync up after reopening an Incident | Test to verify that the state of a child Incident synchronizes with the parent Incident when the parent Incident is reopened. | Madrid |
| INCIDENT MGMT: Verify creation of knowledge article from an Incident | Test to verify the creation of a knowledge article from an Incident using the Create Knowledge UI action on the Incident form. The UI action is visible when you activate the KCS Integration for Incident Management plugin (com.snc.incident.knowledge). | Orlando |
To learn more about Incident Management, see Incident Management.
Incident Management in Service Operations Workspace
Incident Management in Service Operations Workspace quick start tests are available in the base system when you install or update to Service Operations Workspace ITSM Applications (sn-sow-itsm-cont) 6.0 version.
| Test | Description | Release version |
|---|---|---|
| SOW Incident: Create problem from incident | Test to verify the creation of a problem record from an Incident using the Create Problem UI action on the Incident form. | Xanadu (August store release, 6.0 version) |
| SOW Incident: Verify Assign to me button functionality | Test to verify the assignment of the incident record to the logged-in user using the Assign to me UI option on the Record information side panel of the Incident form. | Xanadu (August store release, 6.0 version) |
To learn more about Incident Management in Service Operations Workspace, see Incident Management in Service Operations Workspace.
Integration Commons for CMDB
| Test | Description | Release version |
|---|---|---|
| CMDB INT: Set Test Session Application | Modify the run server-side script to set an application name so that you can test only one integration. Otherwise, all integrations installed will be tested. | Paris |
| CMDB INT: Test Against Source Analysis | Test an integration against the values in the CMDB Integration Source Analysis [sn_cmdb_int_util_cmdb_integration_source_analysis] table. | Paris |
| CMDB INT: Validate Application Feed | Validate all application feeds in an integration. | Paris |
| CMDB INT: Validate Discovery Source | Validate that the discovery source exists. | Paris |
| CMDB INT: Validate Entity Mappings | Validate all entity mappings of an integration. | Paris |
| CMDB INT: Validate Fields | Validate fields for CMDB Integrations. | Paris |
| CMDB INT: Validate Lookups | Validate CMDB integration lookups. | Paris |
| CMDB INT: Validate Mandatory Operations | Validate that all integrations for mandatory operations exist for mapped fields. | Paris |
| CMDB INT: Validate Operations | Validate all operations for an integration. | Paris |
| CMDB INT: Validate References | Validate CMDB integration references. | Paris |
| CMDB INT: Validate Related Entries | Validate all related classes against the data dictionary for related entries. | Paris |
| CMDB INT: Validate Relationships | Validate CMDB integration relationships. | Paris |
To learn more about Integration Commons for CMDB, see Integration Commons for CMDB.
Investment Funding
The Investment Funding quick start tests require activating the Investment Funding - ATF Tests plugin (com.snc.investment_planning.atf).
| 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 |
To learn more about Investment Funding, see Investment Funding.
Knowledge Management
Knowledge Management quick start tests require activating the Knowledge Management Core plugin (com.glideapp.knowledge), the Knowledge Management Advanced Installer plugin (com.snc.knowledge_advanced.installer), the Knowledge Blocks plugin (com.snc.knowledge_blocks), and the Customer Service Management Demo Data plugin (com.snc.customerservice.demo).
| 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 theScheduled 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 |
To learn more about Knowledge Management, see Knowledge Management.
Leader Hub
Leader Hub quick start tests require activating the Leader Hub plugin (sn_egd_lh) and loading demo data.
| Test | Description | Release version |
|---|---|---|
| \[Leader hub\] - Validate LH flows |
Note: Requires demo data. | Xanadu |
To learn more about Leader Hub, see Leader Hub.
Legal Request Management
Legal Request Management quick start tests require installing the following apps:
- Legal Request Management (sn_lg_ops)
- Legal Counsel Center (sn_lg_workspace)
| Test | Description | Release version |
|---|---|---|
| LRM: Privacy Request Test | Tests to validate submission and fulfillment of Privacy legal requests. | Utah |
To learn more about Legal Request Management, see Legal Request Management.
Major Incident Major Incident Management
Major Incident Management quick start tests require activating the Incident Management - Major Incident Management plugin (com.snc.incident.mim).
| Test | Description | Release version |
|---|---|---|
| MIM: Create a Major Incident | Test to verify the creation of major incident from the application navigation module. | Orlando |
| MIM: Create a Major Incident Candidate | Test to verify the Create a Major Incident Candidate module from navigation menu. | Orlando |
| MIM: Create a Major Incident from a Major Incident Candidate | Test to verify the creation of a major incident from a major incident candidate. | Orlando |
| MIM: Major Incident Candidate creation when it matches Major Incident Management trigger rule | Test to verify the creation of a major incident candidate when conditions to create a major incident match the major incident management trigger rule. | Orlando |
| MIM: Propose a major Incident (Assignment group empty) | Test to verify auto assignment of major incident candidate when an incident is proposed as a major incident and the Assignment group and the Assigned to fields are empty. | Orlando |
| MIM: Propose a major Incident (Assignment group is not empty) | Test to verify the auto assignment of a major incident when an incident is proposed as major incident and the Assignment Group and the Assigned to fields are not empty. | Orlando |
| MIM: Promote a candidate to major Incident (Assignment group is empty) | Test to verify auto assignment of major incident when a candidate is promoted to a major incident and the Assignment Group is empty. | Orlando |
| MIM: Promote a candidate to major Incident (Assignment group is not empty) | Test to verify auto assignment of major incident when a candidate is promoted to a major incident and the Assignment group is not empty. | Orlando |
| MIM: Reject a Major Incident Candidate | Test to verify the rejection of a major incident candidate. | Orlando |
| MIM: Demote a Major Incident | Test to verify whether a major incident gets demoted to an incident. | Orlando |
| MIM: Major Incident closure | Test to validate the major incident closure functionality. | Orlando |
| MIM: State sync up with ICP and ICT | Test is to verify the state sync up with Incident Communication Plan and Incident Communication Task. | Orlando |
| MIM: ICP attached to an Incident based on conditions and its state sync up with ICT | Test is to verify Incident Communication Plan attached to an Incident based on defined conditions. | Orlando |
| MIM: Resolving MI and PIR | Test is to verify resolving a Major Incident and Post Incident Report. | Orlando |
| MIM: Major Incident workbench layout verification | Test is to verify Major Incident workbench layout verification. | Orlando |
| MIM: Verify communication task from MI workbench | Test is to verify communication task from MI workbench. | Orlando |
To learn more about Major Incident Management, see Major Incident Management.
On-Call Scheduling
Activate the On-Call Scheduling plugin (com.snc.on_call_rotation) to run the On-Call Scheduling quick start tests.
| Test | Description | Release version |
|---|---|---|
| On-Call: Verify request time-off when PTO approval preferences is Not allowed | Verify whether you can request a time-off when PTO approval preferences is set to Not allowed | Orlando |
| On-Call: Create overlapping shifts without selecting a template | Verify whether you can create overlapping shifts without selecting a template. | Orlando |
| On-Call: Create overlapping shifts when allow shift overlap is set to No | Verify whether you can create overlapping shifts when Allow overlap is set to No. | Orlando |
| On-Call: Request time-off when PTO approval preferences is with approval | Verify whether you can request a time-off when PTO approval preference is With approval. | Orlando |
| On-Call: Assign shift managers for maintaining on-call schedules. | Verify whether shift managers can maintain on-call schedules. | Orlando |
| On-Call: Search on-call schedules by user name | Verify whether you can search for on-call schedules by user name. | Orlando |
| On-Call: Search on-call schedules by group name or schedule name | Verify whether you can search for on-call schedules by group name or schedule. | Orlando |
| On-Call: Roster details for overlapping shifts with the escalation rule 'Escalate to incoming shift' | Verify the roster details for overlapping shifts when the escalation rule is set to Escalate to incoming shifts. | Orlando |
| On-Call: Calendar preview with timezone options | Verify whether the calendar preview is available with the timezone options. | Orlando |
| On-Call: Create overlapping shifts by selecting a template | Verify whether you can create overlapping shifts by selecting a template. | Orlando |
| On-Call: Show active shifts | Orlando | |
| On-Call: Make shift draft/publish form shift form | Verify whether you can publish/unpublish a shift and alternate between making the rota Draft and Publish state from the form. | Orlando |
| On-Call: Roster Details for overlapping shifts with the escalation rule 'Escalate to outgoing shift' | Verify the roster details for overlapping shifts when the escalation rule is set to Escalate to outgoing shifts. | Orlando |
| On-Call: Roster Details for overlapping shifts with the escalation rule 'Escalate to all shifts' | Verify the roster details for overlapping shifts when the escalation rule is set to Escalate to all shifts. | Orlando |
| On-call: Verify On-Call workbench | Test to verify the On-Call workbench layout. | Orlando |
| On-call: Hide or show shifts | Verify whether you can hide or show shifts from On-Call calendar | Orlando |
To learn more about On-Call Scheduling, see On-Call Scheduling.
Metric Intelligence
Metric Intelligence quick start tests require activating the Metric Intelligence plugin (com.snc.sa.metric).
| 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 |
To learn more about Metric Intelligence, see Metric Intelligence.
Predictive Intelligence
Predictive Intelligence quick start tests require activating the Predictive Intelligence [com.glide.platform_ml] plugin. In order to execute critical upgrade tests on existing machine learning solutions, you need to create a basic authorization profile named ml_atfin the Basic Auth Configurations table (sys_auth_profile_basic.list). To run the tests successfully, the user attached to the ml_atf authorization profile must have the ml_admin role.
| Test | Description |
|---|---|
| PI: Presence of ML model artifacts persisted in glide | Verify all the trained ML model artifacts are persisted in glide (sys_attachments table) after model training/instance cloning so that ML prediction calls are successful. |
| PI: Valid setup of ML user (sharedservice.worker) in glide | Validate if the ML user in glide (sharedservice.worker) is active and not logged out so that model training is successful. |
| PI: Glide upgrade test for Classification solution | Validate that the classification model prediction on existing active models is producing the same class membership and confidence value results after a glide upgrade. |
| PI: Glide upgrade test for Similarity solution | Validate that the similarity model prediction API calls on active models are successful after a glide upgrade. |
Problem Management
Problem Management quick start tests require activating the Problem Management Best Practice — Madrid plugin (com.snc.best_practice.problem.madrid) and the Problem Management — ATF Tests plugin (com.snc.problem.atf). For all state related test, the Problem Management State Model (com.snc.best_practice.problem.madrid.state_model) plugin needs to be active.
| 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 |
To learn more about Problem Management, see Problem Management.
Project Portfolio Management
Project Portfolio Management quick start tests require activating the PPM Standard - ATF Tests plugin (com.snc.financial_planning_pmo.atf).
| Test | Description | Release version |
|---|---|---|
| PMO: Verify cost plan roll up to project/demand and program | Validate the total planned cost rollup from project and demand to program. | Madrid |
| PMO: Verify cost plan roll up to project/demand, program and portfolio | Validate the total planned cost rollup from project and demand to portfolio. | Madrid |
| PMO: Verify financials of Project created from Demand - Simple Financials | Validate the financial tab fields of a project created from a demand. | Madrid |
| PMO: Verify financials of Project created from Demand - With budget, cost plans, benefit plans | Validate the budget, cost plan, and benefit plan of a project created from a demand. | Madrid |
| PMO: Verify ETC/EAC at cost plan breakdown and project level | Validate the EAC and ETC values at cost plan breakdown and project level. | Tokyo |
| Test | Description | Release version |
|---|---|---|
| Validate state changes of Idea | Validate that the state of idea is changed when an idea is accepted, rejected, or any other task is created from an idea. | San Diego |
| 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 of the tasks is closed as 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 the milestone tasks are closed when their state is changed to Work in Progress after setting the project preference to "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 is changed appropriately for a project in WIP state when the project start date is changed after setting the project preference to "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 when the project planned dates are different than the project task start date after deselecting the project preference "Rollup project start date from tasks". | 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 of a project in Planning or Open state can be updated to a later or earlier date than the current planned start 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 RIDAC flow for Risk | Validate the RIDAC flow for a risk associated with a project. | Quebec |
| Verify RIDAC flow for Issue | Validate the RIDAC flow for an issue associated with a project. | Quebec |
| Verify RIDAC flow for Decision | Validate the RIDAC flow for a decision associated with a project. | Quebec |
| Verify RIDAC flow for Action | Validate the RIDAC flow for an action associated with a project. | Quebec |
| Verify changes in fields of risk form | Validate that any change is the Risk form fields such as Risk rank, Risk value, and Probability is updated successfully upon submission. | Quebec |
| Test | Description | Release version |
|---|---|---|
| Verify RIDAC flow for Risk | Validate the RIDAC flow for a risk associated with a demand. | Quebec |
| Verify RIDAC flow for Issue | Validate the RIDAC flow for an issue associated with a demand. | Quebec |
| Verify RIDAC flow for Decision | Validate the RIDAC flow for a decision associated with a demand. | Quebec |
| Verify RIDAC flow for Action | Validate the RIDAC flow for an action associated with a demand. | Quebec |
| Verify changes in fields of risk form | Validate that any change is the Risk form fields such as Risk rank, Risk value, and Probability is updated successfully upon submission. | Quebec |
| 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 and 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, if the total planned cost is 500 USD, and the planned hours is 10, and you change the planned hours to 20, the total planned cost is updated 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 task as demand and the start date and end date as added for the demand. | 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, on submitting the time card for the operational resource plan associated with that work type, the actual hours in the resource plan and the time card are equal. | 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 |
To learn more about Project Portfolio Management, see Project Portfolio Management.
Project Currency test suite
Project currency quick start tests require activating the PPM Standard Multicurrency – ATF Tests plugin (com.snc.ppm_multicurrency.atf).
| Test | Description | Release version |
|---|---|---|
| Verify cost in project currency on cost plan | Validate the calculation of cost line breakdown with budget reference rate and verify roll up to cost plan and also for the project in project currency. | Orlando |
| Verify benefit in project currency on benefit plan | Validate the calculation of benefit line breakdown with budget reference rate and verify roll up to benefit plan and also for the project in project currency. | Orlando |
To learn more about PPM Standard, see PPM Standard.
Reporting
The Reporting quick start test Automated Test Framework - Reporting plugin (com.glide.automated_testing_impl.report) is active by default or instance reboot.
Note: Reporting quick start tests do not test report access from dashboards. To test dashboards, see Quick start tests for Dashboards.
| Test | Description | Release version |
|---|---|---|
| Report Visibility | Confirm whether reports are still visible to users whom they are shared with. | Madrid |
Software Asset Management Foundation plugin Software Asset Management
Software Asset Management quick start tests require activating the Software Asset Management Professional plugin (com.snc.samp). Some quick start tests require activating the following additional plugins.
- Software Asset Management - Spend Detection (com.sn_sam_spend)
- Software Asset Management Professional for Microsoft (com.snc.samp.microsoft)
- Software Asset Management Professional for SAP (com.sn_samp_sap)
- Software Asset Management Professional for Oracle (com.snc.samp.oracle)
- Software Asset Management - SaaS License Management Integrations (sn_sam_saas_int)
| 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 |
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 |
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, a software entitlement using the custom Part Number, and 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 |
To learn more about Software Asset Management, see Software Asset Management.
Security Incident Response
Security Incident Response quick start tests require activating Security Incident Response plugin (com.snc.security_incident) and loading the demo data.
| 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 |
To learn more about Security Incident Response, see Security Incident Response.
Service Level Management
Service Level Management quick start tests require activating the Service Level Management - ATF Tests plugin (com.snc.service_level_management.atf).
| Test | Description | Release version |
|---|---|---|
| SLM: Service Level Management Task SLA completed workflow | Tests that a user can create a task SLA and complete the workflow. | Orlando |
| SLM: Service Level Management Task SLA cancelled workflow | Tests that a user can create a task SLA and cancel the workflow. | Orlando |
| SLM: Service Level Management Task SLA timer REST API | Tests that the SLA Timer API response matches data expected by SLA Timer Seismic component. | Paris |
To learn more about Service Level Management, see Service Level Management.
Service Mapping
Service Mapping quick start tests require activating the Service Mapping (com.snc.service-mapping) plugin and loading the demo data.
| 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 |
To learn more about Service Mapping, see Service Mapping.
Service Portfolio Management Premium
Service Portfolio Management Premium quick start tests require activating the Service Portfolio Management Premium plugin (com.snc.spm).
| 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 |
To learn more about Service Portfolio Management Premium, see Service Portfolio Management Premium.
Skills Management
Skills Management quick start tests require activating the Skills Management plugin (com.snc.skills_management).
| Test | Description | Release version |
|---|---|---|
| Skills MGMT: User skill level inheritance when user is part of multiple groups | Verify that the user is assigned the highest skill level when the user belongs to multiple groups that have been assigned the same skills with different skill levels. | New York |
| Skills MGMT: Add skills to lowest level category | Verify that skills can be added to the lowest level category. | New York |
| Skills MGMT: Create a child category under a parent category | Verify that a lower-level category can be created when the flag for Add skills is unchecked in the parent category. | New York |
| Skills MGMT: Create a skill category | Verify that a skill category can be created on the skill category form. | New York |
| Skills MGMT: Create skill level type and skill levels | Define the skill level type and different skill levels for the type. | New York |
| Skill MGMT: Skill level inheritance from group to user | Verify that skill levels can be inherited from a group to the users of the group and that the Inherited and Skill level inherited fields are set to true. | New York |
| Skills MGMT: Create a skill from Manage IT Skills user interface. | Verify that you can create a skill from the Manage IT Skills user interface. | Orlando |
| Skills MGMT: Add skills and skill levels to users in the Manage IT Skills user interface. | Verify that you can add skills and associated skill levels to users in the Manage IT Skills user interface. | Orlando |
| Skills MGMT: Select a skill and add users to the skill in the Manage IT Skills user interface. | Verify that you can select a skill and add the skill and associated skill levels to one or more users in the Manage IT Skills user interface. | Orlando |
| Skills MGMT: Select a skill that does not have a skill level and add users to that skill in the Manage IT Skills user interface. | Verify that you can select a skill that does not have a skill level and add the skill to one or more users in the Manage IT skills user interface. | Orlando |
To learn more about Skills Management, see Skills Management.
Test Management 2.0
Test Management 2.0 quick start tests require activating the Test Management 2.0 plugin (com.snc.test_management.2.0). and the Test Management 2.0 - ATF Tests plugin (com.snc.test_management.2.0.atf).
| Test | Description | Release version |
|---|---|---|
| Create test version should create test | Validate test creation and version. | Madrid |
| Should be able to mark test version as ready when it contains verification steps | Validate test state when test has verification steps. | Madrid |
| Should not able to mark test version as ready when it does not contain verification step | Validate test state when test does not have verification steps. | Madrid |
| Marking a test version as ready should retire other test version in ready state | Validate test state when marking test ready. | Madrid |
| Test | Description | Release version |
|---|---|---|
| When test run closed, should update execution suite progress | Validate execution state progress. | Madrid |
| Should not be able to assign a test not in ready state | Validate test assignment. | Madrid |
| Test progress should roll up for test plan and test cycle | Validate test progress for test plan and test cycle. | Madrid |
To learn more about Test Management 2.0, see Test Management 2.0.
Universal Request
Universal Request quick start tests require activating the Universal Request (com.snc.universal_request), Universal Request: Integration for Incident management (com.snc.incident.universal_request), and Human Resources Scoped App: Core (com.sn_hr_core) plugins.
| 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 |
Vendor Manager Workspace and Third-party Risk Management
GRC: Vendor Manager Workspace and Third-party Risk Management quick start tests require activating the Vendor Manager Workspace and Third-party Risk Management plugin (com.sn_vdr_risk_asmt) and loading demo data.
| Test | Description |
|---|---|
| GRC: Create Engagement Risk Assessment | Creates and submits an engagement risk assessment to an engagement. |
| GRC: Vendor Risk Scoring - Cancel assessment for engagement | Verifies a request to recalculate a risk rating is automatically created on an Engagement and Third party after one assessment for the Engagement is cancelled. |
| GRC: Vendor Issue ATF | Creates and submits a third-party risk issue form and third-party risk task form. |
| GRC: Create Vendor Risk Assessment | Creates and submits a vendor risk assessment to a vendor. |
| GRC: Vendor Portal - Answer and Return Assessment | Vendor contact answers and submits assessment in the Service Vendor Portal. |
| GRC: Vendor Tiering Assessment | Selects and submits an assessment to respective assessors after changing the duration. |
Verify that TPRM still works after you make configuration changes such as applying an upgrade or developing an application. Copy and customize the quick-start tests to pass when using your instance-specific data.
Vulnerability Response
Vulnerability Response quick start tests require activating the Vulnerability Response application (sn_vul) and loading the demo data.
| Test | Description | Release version |
|---|---|---|
| VR: Create Remediation Target Rule | Create a Remediation Target Rule. | Madrid |
| VR: Create Vulnerability Group Rule | Create a Vulnerability Group Rule. | Madrid |
| VR: Create Vulnerable Item via Form | Determine whether a user can successfully create a vulnerable item from the Vulnerable Item form. | Madrid |
| VR: Vulnerability Group Life Cycle | Determine whether a user can successfully resolve a vulnerability group. | Madrid |
| VR: Vulnerable Item life cycle | Determine whether a user can successfully move a vulnerable item through its life cycle, and also determine whether a closed vulnerable item can be reopened. | Madrid |
| VR: Rollup Calculator | Determine whether the rollup risk calculator can provide an overall risk score for an entire group of vulnerable items using the scores for all the vulnerable items in a vulnerability group. | New York |
| VR: Vulnerability Response Assignment Rules | Determine whether a sample set of assignment rules can successfully auto-assign vulnerable items to an assignment group for remediation. | New York |
| VR: Vulnerability Calculators | Test the vulnerability calculators. | New York |
| VR: CI Lookup - Qualys | Create a new lookup rule with method "field_matching" called "Lookup By Network Adapter" for Qualys. Determine whether a configuration item is successfully matched in the Discovered Item table by network adapter and IP address with the new lookup rule. | Orlando |
| VR: Create Normal and Emergency Change Request | Determine whether the user can successfully create normal and emergency change requests from a vulnerability group. | Orlando |
| VR: Split Vulnerability Group | Determine whether the user can successfully split a vulnerability group. | Orlando |
| VR: Update VG state when a CHG is cancelled. | Determine whether the State field on a vulnerability group successfully transitions when a change request that is associated with the vulnerability group is cancelled. | Orlando |
| VR: Update VG state when a CHG transitions to Review. | Determine whether the State field on a vulnerability group successfully transitions when a change request that is associated with it moves to the Review state. | Orlando |
| VR: CI Lookup - Rapid7 | Test CI lookup using the existing Rapid7 Vulnerability Integration lookup rule, IP Address. | Orlando |
| VR: CI lookup - Qualys | Test CI lookup by creating a new lookup rule for the Qualys Vulnerability Integration | Orlando |
| VR: Exception Approval Workflow for VI | Create an exception request and verify that the approval process is working. | Orlando |
| VR: False Positive Approval Workflow for VI | Create a false positive exception request and verify that the approval process is working. | Orlando |
| VR: Application Vulnerability Response (AVR) | Determine whether your rules and calculators are working correctly. Verify that updates are working. | Orlando |
| Remediation target rules: VI import test | Tests VR remediation target rules during import. | Paris |
| VR: Classification Rule | A sample classification rule that automatically classifies a vulnerability. | Tokyo |
To learn more about Vulnerability Response, see Vulnerability Response.
Walk-up Experience
Walk-up Experience quick start tests require activating the Walk-up Experience plugin (com.snc.walkup) and loading demo data.
| Test | Description | Release version |
|---|---|---|
| Create a location | Ensure users with the Walk-up administrator [sn_walkup.walkup_admin] role can access all existing walk-up queues, create new queue locations, and configure queues appropriately. | Orlando |
| Onsite checkin (ITIL User) | Verify that users with the ITIL role can check into an onsite queue location. | Orlando |
| Onsite checkin (ESS User) | Verify that users with the ESS role can check into an onsite queue location. | Orlando |
| Onsite checkin (Guest) | Verify that guest users can check into an onsite queue location. | Orlando |
To learn more about Walk-up Experience, see Walk-up Experience.
Parent Topic:Quick start tests