huge losses not only for software users but even for development companies.
Well-known example is Y2K problem. That's the reason it becomes important to
improve testing and bring it at a level where the software will be reliable. In
making reliable software, software testing plays an important role. It helps in
reducing errors and bugs in the software. These days, there are many automated
software testing tools available that reduce testing job at higher levels and
make it effective to test a software in cost and time efficient way. It is a
responsibility of software tester to point out the error and bugs in a software
and deliver an error and bug free software to the customer.
Here are some tips to be followed for efficient software testing:
Need to make a good test plan: A good test plan covers all areas of
testing a product and considers initial planning, schedule testing, risk
identification, staff acquisition, and more.
Important to understand the product: It is important to understand the
complete project before you start testing. So, during meetings, it is a good
practice to involve tester's right from the software requirements gathering and
architecture design phase. As a result the testers can get knowledge of
application dependability resulting in detailed test coverage. If any tester is
not asked to be part of this development cycle then he/she can make a request to
involve them in all decision making processes. Besides, talk more with
developers to know more about the project.
Test early, test often: When it comes in find bugs in the project, start
early as possible because a bug found during design stage costs less to
eliminate than the one found during the coding stage.
Test positively: Start testing the application with a determination to
find bugs and errors. Don't think beforehand that there won't be any bugs in the
application. If an application is tested with an intention to find bugs, a
tester will definitely succeed to find even the subtle bugs.
Proper test cases improve testing: It is a good practice to write test
cases during requirement analysis and design phases. Test cases should be for
intended functionality i.e. for valid conditions and then for invalid conditions
to cover the expected as well as unexpected behaviour of product.
Test software in small functional modules: Divide software in small
functional modules and make test cases for it. This will ensure maximum test
Develop unambiguous and clear bug report: Report bugs in clear and
unambiguous way so that it is easily understandable. Also, don't only report
symptoms, but also effects of bugs and proper solutions for it.
Maintain test cases for regression testing: Previous maintained test cases
will help in effective regression testing of particular module as well as of
Note down new concepts: Always note down the new concepts that are learned
during testing. Those will surely help in effective testing of future projects.
Author: Robin K Payne