Sunday, 30 March 2008
And now Jan Goyvaerts the author of RegexBuddy has a new blog dedicated to Regexing called Regex-Guru - this quickly found its way into my RSS reader so I recommend it to all testers as it will serve as a useful reminder that the Regex exists and of its capabilities.
Saturday, 29 March 2008
Friday, 28 March 2008
"Me too. Me too. Me too." That sums up my reaction to Antony Marcano's TestingReflections post on interviewing testers that just don't 'come up to scratch'. Those testers we interview who claim to have a passion for testing but don't exhibit said passion.
I've gone through the same as Antony and have no words of advice to offer him, because he probably does the stuff I mention in this post already.
Sunday, 23 March 2008
Wednesday, 19 March 2008
This evening I downloaded and started experimenting with Selenium-Grid when I looked down at my TaskBar and I got lost. I had too many File Explorer window open, and too many command line windows open. Something had to change. Step in UltraExplorer, and Console2.
Tuesday, 18 March 2008
I put my Software Testing Book reviews directly on my Compendium Developments site.
So if you only read Evil Tester then you missed out on Reviews of:
Monday, 17 March 2008
I have done a lot of public talks over the years (but never enough to consider myself 'good' at it). Over the years I have adopted numerous approaches to constructing the presentation and of constructing the slides. You can see some of my worst slides. This slide pack seems better. But overall these slides seem far too wordy and unfocussed. I wanted to see what Beyond Bullet Points (BBP) could help me do. I was pleased with the end results, even though I only partially implemented the system. Had I spent more time learning BBP I think they could have ended up far better. I have no hesitation in recommending BBP to anyone involved in constructing presentations.
Sunday, 9 March 2008
In a previous post I discussed how I managed to do UAT badly in the past. Now I will discuss a generalised model formed from those (and other) experiences, which should allow me to make fewer UAT mistakes in the future.
Saturday, 8 March 2008
The testing tool Selenium goes from strength to strength. As evidenced at the recent Selenium Users Meeting, the future plans for Selenium look really interesting and Google seem to want to continue to invest heavily in Selenium which can only mean good things for the rest of us.
Testers have learned to use abstraction over the years. Abstracting the GUI changes away from the tests with a GUI Map, abstracting the testing language away from the scripting language through 'Action Word Testing'.
Selenium-rc presents us with an API. Around which people tend to build abstraction layers. Many of the people using Selenium-rc use abstraction automatically because they come from a development background. So the simple use of refactoring leads to a degree of abstraction.
Friday, 7 March 2008
I've made a lot of mistakes over the years when testing. I try not to make each mistake more than once - which usually means any future mistakes require more creativity or stupidity on my part. So I will describe some of the mistakes I (and other people I have known) have made when doing UAT so you can use more creativity (or more stupidity - you get to choose) when approaching UAT in the future.
Wednesday, 5 March 2008
Previously I described how I made some TDD mistakes and fixed them by tracking them. And now to help me maintain my good behaviour and reduce my recidivism rate, I install some eclipse plugins: Emma, FindBugs, PMD and mousefeed.
Tuesday, 4 March 2008
For the longest time I didn't know what dependency injection meant - anytime I looked it up I glazed over thinking it really complicated.
I only recently found out while learning TDD that I can describe dependency injection in terms of - pass an object in as a parameter instead of instantiating it in the class or method.
But as soon as I learn this, I encounter a presentation that would have taught me this anyway - so I pass it on now in case you don't know what dependency injection refers to.
The following presentation on 'testability' (from a developer's perspective, i.e. how do you make your code testable) has a good summary slide that makes dependency injection seem simple.
Saturday, 1 March 2008
Previously I made some TDD mistakes. So to fix them. I tracked them.
I tracked the mistakes by creating an index card that listed the 'bad' things on one side, and the 'good' things on the other side. Then noted when I did the bad things, and when I did the good things. The writing of these statements seems important. So if we have a look at the card...