What are best practices for project testing?

What are the best testing practices for IT?

Tests have a huge impact for project costs and on solution quality in production.

Unit test, integration test, user acceptance test

Who’s next to discover the sensation that it went wrong?

We must understand how choices made on the tests results  influence of project costs and solutions behaves. Does unit test mean that it will done only once. Is the succesful result of an integration test the desintegration of the project manager? Are user acceptance test an attempt to sell a donkey like a competition horse?

Effect of non-testing?

First, the lack of testing often increases nonconformities that may affect:
– Internally by loss of time or rework.
– Externally by the commitment of its liability, guarantee or a lost opportunity.

Effect of late testing?

Second, tests may come too late in the process and rose the project costs.We will see how best practices tend to integrate testing throughout the development cycle.

Other methods to increase quality.

Third, tests are just one tool among many to reduce non-quality. Other prevention tools to prevent non-qualities are:

– Training

– Documentation of processes

– Use proper equipment for the function

– The use of audit time and / or proofreading, inspections

Last but not least, overlapping tests and retests may also increase project costs for an equivalent result.

What are best practices for testing?

Tests should be planned at the earliest and organize the test coverage to achieve aquality product at a set price. To achieve this goal, we need several testing approaches.
The tests are the basic tool to validate a step in a process of production and / or creation. We can distinguish different approaches:
– The black box testing
– The white box testing
– The gray box testing
– The iterative testing

The black box testing, You take the delivrable  and put it in a situation as close as possible from the real situation and see the results.

The white box testing uses simulation the test before the delivrable under test is completed. This type of test is based on pseudo-codes or models.

The gray box testing is based on analyze of the deliverable design and possible extreme situations and then test them.

The iterative testing is used in methods like SCRUM. The object under test is built in pieces and testing as well.

The symbiosis of testing methods!

The black box testing is the most common method, but it often happens late in the design and delivery process. The white box testing makes it easy to validate a specification and save time in a project. The gray box testing can improve the robustness of the solution. Iterative testing can keep in touch with the user to validate step by step the final deliverable. So all the tests approachs should be planned and used at the right time. Using this strategy, you can ensure the quality of the deliverable, but also reduce costs and ensure reliable budgets developments.

Fév, 27, 2012