Testing and ServiceNow

General Add comments
by:

In addition to the blog by Fred van der Schaar about Business Requirements, also a test registration module is developed by 2e2 Consulting.
I have been working with this test registration module for a couple of months now.

When Business Requirements and Functional Specifications are defined and new functionality is developed, testing also kicks in. Testing your Functional Requirements and therefore verifying your Business requirements give you the opportunity to check if your ServiceNow instance is working as designed.

The Structure

Currently Business Requirement and Functional Specification are linked to each other. As we are defining the actual adjustments to the tool in Functional Specifications, we have created a link to the Test Case Step (which contains the test criteria). The Test Case Step is linked to a Test Case (which is a summary of all similar like Test Case Steps). Eventually, the Test Case Step contains all test results.

Test Case Steps

The Test Case Steps are based on two parts. An ‘Action to Perform’ and a ‘Expected Result’. In the action to perform we summarize the steps that are needed to be preceded during testing. The expected result provides the tester a clear view of what should be the outcome of the test, so the tester can verify if the Test Case Step is executed successfully. Eventually, the Test Case Step will contain the valuable test results, in a clear list on the bottom of the Test Case Step.

Test Result

The test result contains actually the most important information during and after testing, the test findings. A test result is based on a couple of important variables and essential information during test reviewing. E.g. who registered the test result, the status of the test result (successful or non-successful) and for what instance (Development, User Acceptance or Production) the test finding occurred. In a test result the tester can log the test findings, if preferred there is a functionality to upload attachments (for sample screenshots).

The other part of the test result is the ‘Corrective Action’. This is the field where the developer or test reviewer can communicate with the tester and provide the tester with additional test instructions or to inform the user about adjustments made to the tool originating from their test result.

It is also possible to assign non-successful test results to a developer, who can pick up the test result and see if there are any adjustments that need to be made to the tool. The developer can do a quick assessment to see how much development time the test result requires.

A properly tested ServiceNow system

Using this test structure we are able to verify the functionality that has been created and let the customer easily test if everything is working as expected and desired. We can see for each Functional Specification if it has been successfully tested and if not, it is possible to quickly reassign test results to developers who can pick up the test result. With this test registration module for ServiceNow we are able to perform our test sessions more easily, quicker and with better results.

If you have any questions, please don’t hesitate to email me on: tim.willer@2e2.nl.

One Response to “Testing and ServiceNow”

  1. Ritesh Autar Says:

    Nice story Tim! Very useful.

Leave a Reply