
Regression testing days 3 to 7
This article is part of a series on making regression testing useful rather than painful. The most recent article was (as you would guess from the title to this one) about day 2 of our regression testing adventure.
So far we have been looking at how to do some testing, and then do some basic scripting and mapping as we do more testing. In doing so we have (hopefully) been learning more about the system we are building but our main focus is on making sure it is still performing the way we want to.
Now we are going to evolve our testing onto a proper OODA loop. I have created another article to explain what an OODA loop is, but for our purposes it means this:
How fast and how well can the team move between the following 4 tasks?
- Observe the world around them – the way users are operating, the way the system is performing and the way things are coming together.
- Orient themselves or make sense of all that data (interpreting, analysing, integrating and assessing).
- Decide what to do next with all that information.
- Act on their decisions as a cohesive group.
To do this we need a little lesson in OODA regression testing theory