About every four months, Shrini Kulkarni convinces me to drop the term “Test Automation” from my vocabulary. After all, testing is a creative, thinking process. We can automate some steps […]
Ruby Vs. Python for Testing
There is an interesting discussion going on on the Agile-Testing Yahoo Group right now, about the differences between Python and Ruby. It is oddly reminiscent of conversation I’ve had a […]
My theory of software testing – I
What’s the right mix of exploratory testing, “planned” manual testing, and test automation? My short answer is “it depends.” Now, you don’t need to point out that “it depends” is […]
Do you document your test cases?
We are debating the value of software testing standards right now on the context-driven testing list. Here’s my latest post … >and by the same token writing test cases doesn’t […]
Microsoft Tester Center
Microsoft announced it’s new ‘community’ for software testers last week at STARWest. The ‘community’ (which is a fancy name for a combination webzine, blog, and forums) is located here. Cynical […]
Software Fiction
Jon Bruce continues to improve as a writer. He’s got an excellent series going on now called “Startup” – click here, scroll to the bottom of Startup, and read upwards. […]
What’s a "Test Framework"?
Shrini Kulkarni has been after me to define my terms; after all, I keep writing about “Test Frameworks” but I’ve never defined the term. Wikipedia defines a framework as “A […]
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 […]
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 […]
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. […]
Testing the Stapler
To answer the Stapler question, Mike Kelly referred me to this post where he had 144 tests. Yes, 144 tests, and, offhand, they look to be real, valid tests. To […]
Test Automation – IV
Right now one of the “louder voices in the room” for test automation is the “Agile” test automation voice. And by that I mean something very specific – that you […]
Test Automation – IV
Reads of Creation Chaos has left some amazing comments on the previous post; if you haven’t read them, please take a gander. First off, I agree with Shrini that “regression” […]
Test Automation – III
Charlie Audritsh asked: “I take you to mean what I’d refer to as a regression test. A test of mostly the old functionality that maybe did not change much. So […]
Test Automation – II
I got some great comments yesterday – Charlie and Scott made some solid points, and they are points that I will address. However, before I get there, I would like […]
Test Automation – I
(Taken From a recent post fo the software-testing email list) It always amazes me when strong people come out and say publicly something that I have been mulling on for […]
GreenBar is the New Black
(Or: My Code Odyssey) So, I had a big, nasty codebase. No current documented requirements; a few scattered historical documents. New Requirements of: “Make it to what it did before, […]
Dev to Tester Communications
Last week I posted the comic where the tester says “Hey dev guy, your tests suck! They aren’t actually testing anything!” And the dev guy replies something like “You’re just […]
Tester/Dev Communications
The space between computer programmers and testers is shrinking – but there are still a lot of communications problems. For example, when I first met Harry Robinson, he was working […]
New Article on DDJ.com …
This week I published Are Tests Requirements? which is inspired by a discussion on the agile-testing list. As always, I appreciate any feedback.