CAST 2014 Keynote - Test Cases are Not Testing: Toward a Performance Culture
HTML-код
- Опубликовано: 17 авг 2014
- "Test Cases are Not Testing: Toward a Performance Culture" by James Bach
Testing means evaluating a product by learning about it through experimentation. This is a dynamic, exploratory process. Although we might script parts of it, and even reduce some of it to programmatic fact checks, testing itself is a live performance. In fact, all technical work is a live performance. Programming, managing, designing...it's all a performance. Meanwhile, for many years, some managers have dreamed of making technical work into a factory activity. That would require thinking of testing, for instance, as being encoded in artifacts such as "test cases." The primary aim of that effort is to turn testing into a commodity and to devalue testers. To fight back we need to become better at explaining "performance culture" and better at arguing for what can and cannot be done with a script. 
Наука
The initial article which james mentioned in the beginning "Test Cases are Not Testing: Toward a Performance Culture" @ www.testingtrapezemagazine.com/wp-content/uploads/2015/10/TestingTrapeze-2014-February.pdf
Yes, yes, yes!!!!
At 45:40, the thing about low risk situations sounds plausible but in my experience it is clearly NOT true when dealing with monolithic legacy code (>10 years in production) due to the accumulation of an incredible amount of dependencies in the code that make innocuous changes cause bugs in seemingly unrelated places.
does anyone know if there are any practice tests for the CAST certification. I am looking to take this soon but want to make sure i am prepared for the type of questions being asked. Thanks.
56:32 People in 2020 be like "Google Glass" Reference, oh how cute!
Love the slide around 40:00 -- would any other profession promote "automated" itself.
Ppp
Pp
P
Man, what is going on with the volume levels....
It seems to me it's mostly the term "test automation" Mr. Bach has an issue with. Test automation is to testing as a calculator is to math: both are tools to let computers do what they do better than humans, and neither is stupid/toxic/useless when used in the proper way (and he did use an automation tool in his example!). I understand Mr. Bach frustration when having to deal with people who believe an automated test is an alternative to a human, but he seems to be trolling a bit in his way to express his objection..
I wonder how he would feel if the method was called something along the lines of "test programming".
Word Origin and History for calculator
n. late 14c., "mathematician, one who calculates," from Latin calculator
The speaker at 52:00 was correct that development automation and QA automation are not comparable in the way James was trying to. I get it; he wants to avoid the perception that you can just automate the entirely of the job. He's trying to make a good point (that QA testers can't simply be replaced w/"magical" automation) but using a poor comparison.
This whole test automation thing is just stupid. I don't know for a fact but I think Bach is intentionally trying to stir up controversy by saying "test automation is stupid", but isn't explaining that he only means the word not actually automating stuff like regression testing
Another guru who is trying to sell techne and episteme.