Software test does pay

Software testing as a natural part of development. Testing removes risks of costs. Read also about testing tools and automated testing.

Software test - how do we improve?

With many software developing companies, software testing is getting more and well deserved focus as an important, but previously often downgraded task in the development process. Some experience severities with fatal consequences before test gets priority. Today, it is no longer a matter if we shall test, but how we shall.

Any company developing software with only minor complexity needs effective and structured software testing - it is as simple as that. Deliveries and products must comply with expected quality and requirements through software testing. It is necessary to establish and organize a process for software testing, and to use methods and tools to plan, execute and manage software test.

Are You in control of software testing? Can You improve?

Maturity - start at the beginning

Companies naturally finds themselves on different levels when it comes to maturity in software testing. Some are only about to start and others have reached much further. If you find yourself in the first group, there are some considerations to make before implementing software test.

Many wants to start with automated testing, hoping to save time and resources, which certainly is understandable. Unfortunately many also discovers that automated testing requires much more knowledge, experience and resources than expected. The keyword is maturity. You have to reach a certain level before automated testing pays.

Prerequisites for automated software testing

Automated software testing requires time and resources before return on investment (ROI). When companies decide to invest in automated software testing and the tools required to do so, they first need to do some considerations. You should answer questions like – what is the purpose of testing? What does it take?

Unfortunately, companies often tend to invest large amounts in resources and automation tools, hoping through this road to gain control over and manage all activities of software testing. Sadly, these valuable tools also tend to end up collecting dust on the shelves, just because the company was not ready to conquer the world of software testing

Below, we have listed some of the tasks which continuously have to be handled in order to execute automated software test.

• Preparation of test scripts for all applications and systems to be tested
• Structure and prioritization - and definition of dependencies in test scripts.
• Maintenance of test scripts when functions and screens changes.
• Setting up test environments including configuration of tools for script executions.
• Preparation or collecting of test data – either by creating or extracting from databases and/or files.
• Planning of test executions – who, what and when.
• Error handling during and after test executions.
• Reporting of status and progress.

Agile methods

One of the popular buzz-words in software development and testing is called “agile methods”. It means “to do something fast or quickly”. Agile methods is to some extends comparable with lean.

While talking about agile methods in consumption with development and testing, it means to complete the tasks quicker and more efficiently without the usual “slow” orginazational process. To complete Your development projects with agile methods does not mean that you hereby neglects the processes in development. On the contrary, it is about optimizing Your processes so unnecessary time and resources are not wasted. It is important to understand that the development and testing process must be seen as one process – and not two individual processes. Regardless how You choose to handle the development process – agile methods, or the waterfall method etc. – it is important to have your processes and structures in place.

Structure and process before automation

Automated testing involves many tasks, but primarily to be in control of the test process. A well established organization to take care of the numerous tasks and a structure for keeping and controlling tests has to be created and deeply rooted in the organization. If you have not completed this there is a huge risk that automated testing will fail.

Our belief is therefore that automated testing can certaily be of great valuable for the company, but first the structuring of test and management of the “manual” part has to be in place.

TMMi

There exists a maturity model called TMMi or just TMM (Testing Maturity Model) – The “i” indicates a new (2006) revised version of the model.

The TMM-model is developed through “best practice” over many years by test experts. The model decribes 5 levels of maturity, where level 1 is the first. At level 5 You have full control of test process and methods, together with both manual and automated testing. At TMM level 1 You have only just considered testing - therfore it is also called the initial level. The important fisrt task is to determine Your current maturity level to provide background for new goals in Your software testing.

Read more about TMMi:

www.tmmifoundation.org

The tool is important

An important part of testing is being able to ensure quality, regardless of maturity – is to have a good test management tool to structure and manage the test. The need of a test tool is dramtically increasing. We at BBLsolutions are aware of this fact and the reason why we – with background in many years of experience – have developed the test management system CompassTMS for planning and execution manual testing, and to structure and manage both manual and automated software testing.

For further details about CompassTMS and the benefits of using it in software testing, please follow this link to Products.