Testing (Agile Project)

The goal of any software development project (agile or Traditional) is to meet project requirements. Meeting project requirements means you will finish the development of the Software at the agreed time, you will keep the quality of the product high while keeping everything within the allowed budget. The part of keeping the Quality of the product high is where TESTING comes in. Testing helps to ensure that, the work products are being developed in the correct way (Verification). Testing also ensures that the product will meet the user's expectations (Validation).

Software Testing is a way to assess the quality of the software and to reduce the risk of software failure in operation...

Many a time we see systems fail. And we ask ourselves, what caused the failure? There are many reasons why a system will fail. If we want to avoid these failures, we must either avoid errors and faults or find them and rectify them. And with Testing, we can avoid failure.

An error (or mistake) leads to a defect (or fault), which can cause an observed failure...

When testing a complex product, avoiding all possible failures may not be feasible. This is because exhaustive testing of complex systems is not possible. Testing shows the presence of defect(s) but cannot prove that there are no defects in the Software.

Note: Testing is a part of Quality Control, and Quality Control is part of Quality Management. And for Testing to be effective and efficient, it must start early (even from the planning stage of the project).

Testing can be Dynamic or Static

In Static Testing, Defect in software is checked without actually executing the code of the software while Dynamic Testing checks the defect in software by executing the codes...

Dynamic Testing requires the execution of the product being tested. Static testing does not require execution of the product or any part of the product being tested but involves the assessment of the code or other work products being tested. Work products can be documentation or code.

Difference between Testing and Debugging

Although both of them are very essential in Software Development, however testing and debugging are different kinds of activities. Testing can show failures that are caused by defects in the Software. Debugging is the development activity that Software Developers go through to identify the cause of bugs, or defects in code, and fixed such defects. Testing does not include correction of defects; however, it ensures that changes and corrections are checked for their effect on other parts of the component or system. And his is called Regression Testing.

Why is Testing Essential

1. Testing is done to reduce the risk of failures occurring during product usage
2. Testing is done to examine work products
3. Testing is done to check if all the agreed requirements have been satisfied
4. Testing is done to see whether the item under test is complete, and meets the Stakeholders expectations
5. Testing is done to build confidence in the quality of the item under test
6. Testing is done to prevent defects
7. Testing is done to find failures and defects
8. Testing is done to give sufficient information to enable decision-makers to make decisions from the point of view of quality
9. Testing is done to comply with contractual, legal, or regulatory requirements or standards