Automated tests, as a product, should be available for use by any tester (and other team members) with minimal technical skills required. This requirement heavily applies to the following procedures: Automation setup before execution. Launching execution of scripts. Reviewing test execution reports. This requirement somewhat applies to the following procedures: Performing project-specific environment […] ...
Transparency of coverage should include written information about the following: Implemented Test Coverage – coverage of each and every automated test case, including test purpose and main execution steps. Executed Test Coverage – automatically generated test execution report, with each and every automated test case that was executed, including test purpose, all execution steps, and […] ...
Creation effort maps directly to costs - one can compare creation expenses with potential savings. Creation effort is an integral characteristic comprising the following: Test design or re-design of manual test cases to convert from human judgment to mechanistic verification. Automation design and development, including creation of scripts and any reusable components. Swiftness and efficiency […] ...
The automation is fundamentally limited to mechanical verification (aka Checking) – through comparison of values only. However, with proper design, automation may simulate many of usage scenarios, which will trigger possible problems either detectable through comparison or directly impacting the flow of test execution. Combination of cheap high volume of automated tests with human attention and […] ...
With years of my career evolution as a testing and automation professional, I’ve developed my own practical view about requirements, their role, and how to deal with them in a context-driven, heuristic way. I’m completely satisfied with the requirements provided by Business. I never require them to be 100% clear and precise, and never complain […] ...
