To test an application or software you need a test plan. This is a document which prescribes the procedure and order of a single software testing cycle.
We can distinguish 6 stages of any app testing process. Here are they.
Once testing typically began at the end of development life cycle, but now people have understood that this is far too late for such an important part of app development. Ideally, test plan building should coincide with app planning itself, that’s why test developers need participation in analyzing requirements along with code developers. However, testers’ analysis goal differs from that of coders’ since testers interpret these requirements from the end user perspective and they aim at establishing appropriate techniques needed to achieve the customer’s purposes. That’s why testers have to always remember the level of user skill and the environment where they’ll be using the app.
After understanding the requirements you can go on to preliminary test planning where tests may be vague. Remember that requirements are likely to change with time, so the idea here is to build an overall strategy possible to modify and improve with the progress. During the planning mind following testing concepts like parametric limits, test data requirements, “negative” test conditions etc. Another important step is the agreement of having some independent testing environment installed in time.
- Test Design
While designing and developing test cases you should keep in mind several things. Each test case is a separate document which contains an introduction with explanation of the characteristic under examination and the expected results in general. It should be consistent in format and prescribe all needed assumptions and prerequisites. A reference section lists all project requirements to be satisfied by the test case pass. The bulk of a test case contains actual test steps of the procedure. Each test step must perform only just action to get a specific result.
- Test Execution, Making Corrections, Re-testing
During the test execution a risk estimation system has to be in place. The risks of 5 levels should be identified according to their damage to the app. Early at this stage testers and developers should closely communicate to ensure quick and informal problem solving. After corrections are made, frequent retesting may be needed. There’s a necessity to implement a well-documented and more formal defect recording system with the progress of test execution.
- Test Reporting, Closure
After all the formal testing is finished, testers are to make a test report covering the whole testing process. The report will include all major difficulties encountered and defects which are discovered, corrected or existing. The risk level likely to be involved in the product release has to be thoroughly explained as well.
- Post Installation
After the product’s delivery testing is not over as some unexpected fallouts may occur at any time. Developers may make some periodic updates which will open up a fresh bunch of bugs. Now testers are not only concerned with the successful improvement installation, but also must verify that nothing was damaged in existing code during the upgrading.
In the end, each project is individual and has its specific needs. In this article we’ve presented just a starting point for readers to get an insight into the great number of possibilities and opportunities awaiting a diligent software tester.
Created: 13 Feb 2014
LET'S GET STARTED!