Expectations From Automation Test Tool : Expectations From Automation Test Tool Author – Mr. Ashish Abrol
Email – ashish.abrol@grailtest.com
Web – www.grailtest.com
Slide 2 : The tool MUST allow testers to create test scenarios (without the need for them being developers).
Automated test tool SHOULD provide interfaces (GUI and API based clients) for configuring and scheduling automated test suites
Slide 3 : Automated test tool SHOULD provide several modes of running tests – a web interface (primary) and a command line interface
Automated test tool SHOULD use a central repository of test artefacts e.g. for housing scripts, input data, expected results (and after test execution, actual results)
Slide 4 : Automated test tool client MUST have a ‘scheduler’ – to allow a Test Suite to run automatically at a specified future time (for instance, to run overnight)
Automated test tool SHOULD send Test Execution Summary Report automatically via e-mail to the scheduler upon completion of the Test Suite
Slide 5 : When a test case fails, details must be provided of each failure/exception, including as a minimum:
Test Case ID, Error Code, Error Description, Screenshot, Module where error occurred and failing operation if possible as well as any other details that may prove useful about the failure.
Slide 6 : Automated Test tool MUST capturea) Output of a test caseb) Test Case being performed and/or what was happening at point of errorc) Expected Resultd) Actual result
Slide 7 : Thank You!