"It is not automation when..."
summary
Claims that code is "automation" fail when tests need manual intervention like pausing to comment out test code or continuing steps in the browser, when results are unreliable/flaky, when steps lack assertions or validations, or when runs never start automatically. Examples use Selenium tests that open browsers and miss checks, and recommend scheduling runs with CI (Jenkins) so tests execute end-to-end and report dependable pass/fail outcomes.
AI-written summary · about
related talks
16mIsn’t Test Automation a Silver Bullet?
28mAutomation does not replace collaboration
24mWHY ARE WE FAILING WITH TEST AUTOMATION?
51mRedefining test automation
46mWhy Is Test Automation Still Manual and How Can We Make It Really Automated?
01h 48mNo Such Thing as Manual Testing and Other Confusions
47mIs Survival of the Fittest Only for the Fastest?
24mA Comedy of Errors