The Agile manifesto states that you should value working software over comprehensive documentation, but as we all know, this does not mean no documentation. If you’re following an Agile approach for your programme of work or project then we would always recommend considering and documenting your Agile Test Strategy. Here are three things to consider when creating yours.
Within every organisation there are a number of documents that have a hieratical order. When it comes to testing you would expect to find the Test Policy document at the top of the tree; this document is only a couple of pages long but does at executive level spell out the quality needs of the organisation and gives the vision of what is expected of every project. This document is owned by the CIO or IT Director and should be mandated to ensure every programme and project works to the same expected standards every time.
Ever heard the expression ‘More speed, less haste’? Acting too quickly and without due diligence, focus and attention to detail will result in avoidable mistakes and thus require even more time to complete the task satisfactorily.
What if Entry Criteria for Load and Performance Testing are not met?
A little while ago I wrote a blog called ‘What are the entry criteria for Load Testing?’.
As we rapidly approach the new spring season with vigour, there's never a better time to revisit areas in our work/home lives and look at applying a fresh approach to make improvements.
The same can be said for software testing and exploring fresh ways of being innovative in the use of processes, tools and methodologies applied. The new financial year can bring new opportunities to invest in improvement initiatives and the fresh new spring season can often give rise to renewed energy, open mindsets, renewed commitment to try and apply new strategies and look to reduce none value-add activities.
Even with the best will in the world, we all forget to do something at some point in time. Whether that be something trivial like putting out the bins to forgetting to pick up the kids after school…. Yep, that has happened…
For all those budding chefs out there, the question will always be, do you follow a recipe for your meal or do you make it up as you go along? Now, creative and seasoned chefs will throw in the ingredients to produce delightful food, however for us less talented would-be-cooks, our results will be vastly different, and that’s the point. To get predicable results you’ll need to follow a process (recipe) to gain the greatest chance of success - just like adopting an automation test framework.
Lack of Appetite to Test
The most debilitating and possibly biggest challenge I face when it comes to load testing is the lack of appetite to load and performance test from the senior project stakeholders.
Before you can begin to improve software testing in your organisation, you need to refresh yourself as to why testing is so important. It’s very easy to take things for granted; take your car for example, you get in, start it up and drive. You never think it’s not going to start or breakdown. There was a time though when cars were poorly made, forever breaking down and a real source of disappointment. Now, cars are largely fault free thanks to advanced engineering and software design and of course very thorough testing. There are millions of lines of code in each modern vehicle, and each line of code has been tested many, many times under many conditions to ensure a fault free drive. Some cars, as I write this article are achieving Level 3 Car autonomy - drivers are still necessary in level 3 cars, but are able to completely shift "safety-critical functions" to the vehicle, under certain traffic or environmental conditions.
As you might have realised the modern world is moving and developing at an alarming pace, change within our daily life is rapid, and just about everything we do in some way has been enabled by a computer and each application has been developed and (hopefully) tested. The desire to do more and do it quickly for less is forever in demand. Change is here to stay and organisations need to be ready to cope with the ever-increasing mandate for speed of delivery and first-class quality.