Before testing an application testers should follow the following activities. Read the below points before test any
application,
1) Learn to
analyze your test results thoroughly.
Analysing the results and inputs avoids so many mistake or misunderstanding in
application.
2) Learn to
maximize the test coverage every time you test any application. [mapping with
testcases]
Test Coverage:
Features to be tested & Features not to be
tested:
For a single functionality lots of scenarios
are there to test. Most of the time testers may miss or omit the some of their
test cases and complete their test. But in real time environment it causes
major problem. So tester need to carry their test and map with their test cases
every time
3) Write
test-cases for Valid first, to avoid problems in major functionality
Every tester
should know how to write test-cases how to map with our application. On reading
the test-cases anyone can easily understood the functionality of the application.
Documents need
to prepare:
Tester need
to prepare a separate document for everything which helps them to face any
problem.
Sanity test
case, Functional test case, Scenario based, error guessing etc..
4) To start
testing the applications prioritize urselves and start to test don’t run out of
time to do high priority testing tasks. Prioritize your testing work from high
to low priority.
Plan
according to that to avoid risks in application
5) Write
clear, descriptive, unambiguous bug report it should be clean, simple and
reusable and easy to understand.
6) Enlarge
your communication with application users to know more about the product.
7) Testing
teams should share their knowledge best testing practices, experience with
other teams in their organization. This makes everyone to think in distinct way
and make them to learn so many new things.
8) It is must
to involve tester’s right form all the phases. So that they understood the
entire flow of the application and improve its quality.
9) After
start testing the application Keep developers away from your test environment.
They may argue with you while testing their task was perfect.
10) Write
your test cases in requirement analysis and design phase itself. This way you
can ensure all the requirements are testable. And you will get some confidence
level about your application with its domain knowledge.
11) While
doing regression testing use previous bug graph (Bug graph – number of bugs
found against time for different modules). This module-wise bug graph can be
useful to predict the most probable bug part of the application. Which part of
the module was with more bugs and try to estimate it.
12) Applications
requiring critical response time should be thoroughly tested for performance.
Performance testing is the critical part of many applications. In manual
testing this is mostly ignored part by testers due to lack of required
performance testing large data volume. Find out ways to test your application
for performance. If not possible to create test data manually then write some
basic scripts to create test data for performance test or ask developers to write
one for you. Most of the automation tools was also available with free of cost
to do performance testing.
13) If
possible identify and group your test cases for regression testing. This will
ensure quick and effective manual regression testing.
14) Go
beyond requirement testing. Test application for what it is not supposed to do.
15) make
your test cases available to developers prior to coding. Don’t keep your test
cases with you waiting to get final application release for testing, thinking
that you can log more bugs. Let developers analyze your test cases thoroughly
to develop quality application. This will also save the re-work time.
For Trainees
ask your Team Lead and Project Managers for sign off the test cases document
before starting testing.
