Skip navigation.

Archives

Scrum + Manual Testing methodology (for WEB apps.)

agile
I believe there are two wrong ways to add the formal QA to Scrum: to give up manual testing skills and learn automation or give up agile principle of quick feedback and test one iteration behind. There is a better way and I’ve seen some articles struggling around with generic phrases like collaboration, optimization, exploratory testing. But none describing the methodology.
What follows is a theoretical research (based on different resources) trying to define such a methodology. The main idea is to add new role (beside the team, scrum master and project owner) called a tester. The methodology sounds very logical. Why nothing like this has been published beforehand? Am I missing a lot of issues with this methodology? Anyone willing to apply it?! Please e-mail ojnjars@inbox.lv if you are willing to contribute this research.

Testing, Contracts, Agile and Axioms

Many, many thanks for the invitation to speak and the hospitality of the Dansk-IT Test Manager Klub. A very welcoming audience for my 'traditional' pitch on Contracts and Testing and also the discussion on Axioms and Agile. Thank-you.

You can see the Axioms talk and paper here. The Agile Contracts slides are attached to this post. Also, the Axioms Worksheet I used in the session.

Interactions at GLSEC

The CEO of my current company will be giving a talk at this year’s Great Lakes Software Excellence Conference . In the talk, Michael Cloran is planning on showing off our software, talking about the technology hurdles that Interactions needed to overcome to get to where we are, and talking about what’s needed in order [...]

GUI Test Automation Considered Harmful

I have been saying this for years, and Alan Page finally posted about it:

GUI Schmooey
"The point is that I think testers, in general, spend too much time trying to automate GUIs. I’m not against automation – just write automation starting at a level below the GUI and move down from there."

The GUI tends to be the most fragile layer of an application. It also tends to be the layer where a lot of automated test infrastructure is built. I don't like this style of "black box automation". It is tempting to automate a regular user's UI experience; and indeed this can be useful. However, in most cases, you are not being as productive as you could be by taking a manual/unscripted approach to your GUI functional testing.

So Much For The Free Market

Hey, maybe I can get my business underwritten by the taxpayer, too?

You can bet your bottom dollar that US workers will be paying for this bail-out for decades to come. And the UK government has also made many billions available to banks to help fill the gap left by toxic debts (by which we really mean "loans they shouldn't have given".)