@#%!, Jim…I’m a Tester, Not A Programmer
summary
Argument: testers without programming degrees can still automate useful tasks by chaining command‑line text tools. Uses findstr on Windows, pipes and a simple batch file that accepts filename patterns to locate log lines with "incomplete" and "timeout", and shows equivalent commands (PowerShell Select-String, grep) on Unix. The concrete pipeline extracts the few relevant lines from thousands, is repeatable, parameterizable, and saves manual triage; caveat: codeless GUI tools hide maintenance costs over time.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:47Automation Needs Coding!!!
- 1:07Codeless Automation To The Rescue!!!
- 5:56Example Log File
- 8:20The Pipe Operator
- 9:26That's The Stuff!
- 14:46Takeaways
related talks
37mThe Lazy Tester
24mA Comedy of Errors
40mAutomated acceptance tests for terminal applications
03h 02mPowerShell Unit and Infrastructure Testing
44mPolyglot automation
40mBenjamin Bischoff: Old Tools, New Tricks: Unleashing the Power of Time-Tested Testing Tools
49mHow to Optimize Automated Testing with Everyone's Favorite Butler
47mIs Survival of the Fittest Only for the Fastest?