Information Technology Reference
In-Depth Information
implementation projects where not much change is required in packaged software
that is being implemented (plain vanilla implementations). This also happens when
a quick, small new version has to be introduced in the market. In such cases, test
managers are left with managing the show without proper planning. How should
you deal with such a situation?
Here is help!
We are providing a way to deal with such situations. Of course, it is not all roses
on the way, and this help should not be used where detailed planning is a must for
the project.
We can quickly go through the SRS document first to identify high-level functions
of the project. Write them down. Once this is done, identify the other functions.
The strategy for test cases should be to find out negative, positive, and bound-
ary value analysis for all test cases. One factor that helps in faster testing is to
find out common mistakes that users make while using any application. For
example, people make silly mistakes when they do not follow instructions writ-
ten about filling input boxes. For password fields, some instructions are given
such as “The field should contain at least six characters and should contain at
least one numeric value.” So check these conditions in the application and make
test cases for these conditions.
You should also make priorities for test cases. From communication with a
customer, you must have an idea about which areas of testing are critical for the
customer. Prioritize these test areas and test them ahead of other areas.
5.9.1 The Drawbacks
Due to necessity you are sometimes forced to do testing without a proper plan.
If the testing is for a new version of the application and if your team has been
working on this application for some time, then testing without a plan is not a
big issue. It happens in such scenarios, and it is not a big deal. In these scenarios,
everybody on the team is familiar with the application and many people on your
team may have developed competency for specific modules or specific types of
testing. So it is absolutely normal to have this scenario and nobody complains
much.
But if the application is new for the team, then definitely this approach has
certain limitations. Some of these limitations include the following:
functional aspects of the application.
No risk management—Definitely without proper planning, risks cannot be
Incomplete functional coverage—This kind of testing can never cover good
ascertained, measured, or managed.
Difficulty in reproducing defects.
Search WWH ::




Custom Search