More and more customers are telling us they want to shift testing left. I’ve just come off a chat session from our website where we had just this conversation with a consultant working for a large ServiceNow partner.
‘The problem’, he said, ‘is that the tests can only really be created AFTER the functionality has been created’.
Our chat agent response...
‘Yes that is normally the case, but not with our AutotestPro. We are big advocates of TDD and ATDD, so the business scenario can be created in advance, in the form user actions that are flagged as 'new requirements'. When these user actions are flagged as such, they even automatically create development tasks. Once these development tasks have been completed, the developer turns of the 'new requirement' flag and it becomes an actual test which can be run automatically in the test engine’.
Shift left testing is only achievable if you have a solution which allows you to effectively define ‘requirements’ as ‘future tests’. Test Driven Development (TDD) is not new, but solutions which enable this are few and far between.
Even rarer are solutions which combine TDD with Continuous Integration Testing and Continuous Delivery (CI/CD).
Everything we do at AutotestPro, is driven by the desire to see the delighted expressions on our customers faces, when we show them how we automate the impossible in ServiceNow.