Paul Gerrard's blog

The Testing Uncertainty Principle

On Thursday's SIGIST meeting, it was great to have such a positive reaction to my workshop and closing talk.

The Fallibility axiom (p41) tells us our sources of knowledge are undependable. The tester is a human being and prone to error. The system is being tested because we are uncertain of its behaviour or reliability. As a consequence, the plan for any test worth running cannot be relied upon to be accurate before we follow it.

Test Management Summit - Presenter Materials are now ONLINE

Thanks to all the people who sponsored, facilitated, attended and supported the Workshops and the Summit last week.

We've posted the presenter materials on the TMF website here: http://uktmf.com/index.php?q=node/239

NB: you must be a logged-in registered user to see the links to the downloads. If you aren't registered already, you will need to do so here: http://uktmf.com/index.php?q=user/register

Thanks and best regards,
Paul.

Advancing Testing Using Axioms

Last week I presented a talk called "Advancing Testing Using Axioms" at the First IIR Testing Forum in Helsinki, Finland.

Test Axioms have been formulated as a context-neutral set of rules for testing systems. Because they represent the critical thinking processes required to test any system, there are clear opportunities to advance the practice of testing using them.

The talk introduces "The First Equation of Testing" and discusses opportunities to use the Axioms to support test strategy development, test assessment and improvement and suggests that a tester skills framework could be an interesting by-product of the Axioms. Finally, "The Quantum Theory of Testing" is introduced.

Go to the web page for this talk.

Is Testing Last in Line?

A post on the Software Testing Club, Is Testing Last in Line? seems oh so familiar to complaints (if that that is they are) heard for as long as I've been in software (and I'm in my 29th year).

I think all of the responses to the blog are reasonable - but the underlying assumption in all (most) of them is that the tester is responsible for getting:

a) involved early
b) involved heavily

Is anyone researching HOW to choose a test model?

The Project Euler site presents a collection of 'maths-related' problems to be solved by computer - 250+ of them and the site allows you to check your answers etc. You don't need to be a mathematician for all of them really, but you do need to be a good algorithm designer/programmer.

But it also reminded me of a recurring thought about something else. Could the problems be used as 'testing' problems too? The neat thing about some of them is that testing them isn't easy. Some problems have only one answer – they aren't very useful for testers - there is only one test case (or you need simply to write/reuse a parallel program to act as oracle). But others like problem 22 for example provide input files to process http://projecteuler.net/index.php?section=problems&id=22

What is the best ratio of testers to developers in an agile team?

You may or may not find this response useful. :-)

"It depends".

The "it depends" response is an old joke. I think I was advised by David Gelperin in the early 90s that if someone says "it depends" your response should be "ahh, you must be a consultant!"

But it does depend. It always has and will do. The context-driven guys provide a little more information - "it depends on context". But this doesn't answer the question of course – we still get asked by people who really do need an answer – i.e. project managers who need to plan and to resource teams.

Certification - a personal history

As a matter of record, I wanted to post a note on my involvement with the testing certification scheme best known in the UK (and many other countries) as the ISEB Testing Certificate Scheme. I want to post some other messages commenting on the ISEB, ISTQB and perhaps other schemes too, so a bit of background might be useful.

All Testing is Exploratory

All testing is exploratory. There are quite a few definitions of Exploratory Testing, but the easiest to work with is the definition on Cem Kaner's site.

“Exploratory software testing is a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the value of her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project.”

I'm Speaking at Rational User Group Meeting 4 July 2011

I've been asked to speak at the UK Rational User Group meeting on Monday 4th July.Yes, NEXT Monday.

Meeting location: Heritage Motor Centre

Agenda
12:00 - Lunch and Registration
12:50 - Welcome - Julian Holmes
13:00 - Session 1 - Testing with IBM Rational at Capgemini - John Manley, Capgemini
14:00 - Break
14:15 - Session 2 - The Pursuit of Quality: Chasing Tornadoes or Just Hot Air? - Paul Gerrard, Gerrard Consulting
15:15 - Break
15:30 - IBM Rational Update - Anthony Kesterton, IBM Rational
16:00 - Session 3 - Driving Quality through Collaborative Automation - Neil Williams, IBM Rational
17:00 - Summary and Prize Draw
17:15 - Close

Directions
Banbury Road,
Gaydon,
Warwickshire,
CV35 0BJ

http://www.heritage-motor-centre.co.uk/visit/getting-here/

You must register to attend. To register click here

FREE to attend Testing Workshops

Gerrard Consulting are offering the first in a series of free workshops that will focus on advanced skills for test managers and practitioners.

Venue: Balls's Brothers, Minster Pavement Date: 27 July 2011

Business Story Pocketbook

The Business Story Method is supported by and largely documented in a book called "The Business Story Pocketbook" which is available for FREE DOWNLOAD or can be purchased from Gerrard Consulting (or other good booksellers).

The Business Story Pocketbook


Download or Buy the Business Story Pocketbook

Testing Axioms and Pocketbook

The Testing Axioms identify the critical thinking processes for testing. As a set of context-neutral rules they also provide a universal testing framework.

The Test Axioms are defined in The Tester's Pocketbook. You can see the axioms online here: testaxioms.com.

The Tester's Pocketbook


Buy The Tester's Pocketbook here

PGtwitterfeed

Syndicate content