AutoPlan. Capture requirements right.
4 min read
The first in a series of webinars providing a Complete Guide to Testing ServiceNow, kicked-off with a webinar de-mystifying the creation of a Test Strategy for ServiceNow. A recording of the webinar can be found here ServiceNow Test Strategy Webinar Recording
Paul Chorley, CEO and Co-founder kicked-off the session by explaining the difference between a plan and strategy.
"Your Test Strategy document defines the Why and the What and outlines your approach and objectives for testing ServiceNow. The Test Plan is the 'how'; how are you going to confirm that the objectives defined in your Test Strategy have been met."
Paul described how testing PaaS platforms like ServiceNow needs a unique approach. Many of the core features in ServiceNow are provided out of the box. However, he provided a waning that just because something was out of the box, didn’t necessarily mean that it didn’t need testing.
Paul went on to explain, using the story of a fictitious main character Bob a ServiceNow Test Manager, how it is vital that you have a defined Test Strategy and the importance of getting it signed off by senior stakeholders. Bob from the story, had run hundreds of tests, just not the right tests! This resulted in a business critical process failing after a ServiceNow upgrade and the business incurring a significant cost as a result.
"Your Test Strategy effectively defines a compromise between the risk of software failure and the amount of resources you are willing to spend mitigating those resources. Senior stakeholders need to sign off against that defined compromise."
Paul then introduced for the first time the Power Test Strategy Matrix. A simple yet extremely powerful and unique method of determining the prioritization of testing ServiceNow business processes, based on a combination of Business Criticality and amount of customisation from out of the box ServiceNow functionality.
Future webinars in the series will provide further knowledge about testing the ServiceNow platform, including how to test integrations with other systems and how to test in an Agile project landscape.