Or: Test Eye for the Framework Guy Douglas Sellers, The Inkster Guy gave a talk on writing a domain-specific language for testing. His idea is to write the test cases first in a language that looks like a English, then figure out how to write an interpreter for those test cases. (Stereotype warning / warning […]
GTAC – Bonus Section #3:
Another speaker claimed that “The only Exhaustive Testing is when the tester is exhausted” – we agree. By Exhausive Frameworks, I mean the ability to do everything. The problem is that by being _able_ to do everything, we use abstractions that make it hard to do any specific thing. Sometimes, a quick-and-dirty, only-works-for-this-app, only-works-for-this-screen automation […]
GTAC – Bonus Section #2:
We have seen a wonderfully isolated, encapsulated, poly-morphed, design-patterned, auto-tested, mocked app … – That could have been written procedurally in 500 Source Lines of Code– But now consists of 10 classes and 20 files spread over 4000 SLOC Using mock tools results in software with more code (Pettichord, “Homebrew Test Automation”, 2003) If you […]
GTAC – Bonus Section #1
Our GTAC Talk evolved over an extended period, and had a lot more material than the time allowed. So, just for you Creative Chaos readers, I’m going to blog our bonus section. Comments on the Slide Above: If you want to mock out (‘trust’) every domain – including database on db intensive apps, the filesystem […]
Why GTAC is different
As I write this, it’s 3:36PM on August 23rd, and I am sitting at the New York Google Office, just after co-presenting a talk on interaction-based testing. I am sick. Exhausted. Drained. Barely able to give the follow-up speakers the attention they deserve – but I’m trying, they did it for me. And, to borrow […]