Perdy World!! I feel like the crazy old cat lady who just found two cats in a dumpster – I’ve been testing all day long! Not some of those old dull raggedy-ass tests but session-based tests.

Now, you might wonder why I’m writing in English. Don’t be alarmed, I’m not high… today atleast. This is my way to pay homage to my friend James Bach who actually developed Session-based testing and it would be nice if he actually could understand anything. I’m a frequent commentator in his blog. Any how, to break it down for you guys, Session-based testing consists of a few elements: a charter, the agenda for a test session, a session (duh), which is an uninterrupted period of time spent testing, and a session report.
I’ve developed my own testing method, which stems from the session-based, and I’ve coined it Shnessey-based testing.
Now the way I implement Shnessey-based testing is this: lets say we are going to test a tricky and unorthodox function like the login function. Now we’re in for some heavy 60 min of pure focus on the charter goal thinking out of the box.

First I start my session by going to a nearby café ordering some cappucino. I usually sit there for a full 20 min chatting away and/or hitting on random strangers. After this heavy pondering I take around 15 min of playing some online nintendo games. 8-bit games only.

After this breathetaking test of dexterity I’ve got about 25 min left I could spend on some more contemplating on the complexity of the login function, which normally just ends up with 20 min of chatting on msn. Ok, so now I’ve only got 5 min left you say – there isnt more time.

Testing is a never ending story – time is never enough.  I simpy write “not enough time to figure this out” in the session report or I switch reports with one of my collegues.

Good luck testing