Tip 1. Review the application's requirements often.
Sometimes there are no or partial test cases exist for certain requirements.
You may find bugs when you test for these requirements. Be quick and you may
find bugs immediately after a requirement change has been first implemented.
Tip 2. It is possible that
you have created positive test cases only. If so, then create negative test
cases for each requirement as well and test them.
Tip 3. Execute each test
case with a variety of test data (for example by the boundary-value analysis
technique or pair-wise testing technique).
Tip 4. Test the interface
of your application with external systems carefully. This is where a number of
bugs may exist.
Tip 5. Application settings
(this is one area that may be rarely tested in fear that the application may
stop working correctly or stop working altogether).
Tip 6. Repeat your tests
using other supported client configurations (other CPU/RAM/operating
systems/screen resolutions/browsers etc.)
Tip 7. Look at the previous
bug reports against the same application or similar applications. See if you
can test your application using the ideas or information contained in the
previous bug reports.
Tip 8. Do not ignore the UI
bugs. If they would inconvenience a user, they should be reported and fixed.
Tip 9. Create a list of
items that you would like to test if you had the time. When you test your
application, you may find yourself taking mental notes of things that you would
like to test later.
Tip 10. In case you are
working as part of a testing/ QA team, do not restrict yourself to the areas
that you are supposed to test. You may find bugs in the other areas.
Tip 11. Instead of rushing
through your tests at top speed, slow down . You would give yourself time to
think more clearly. You would start to observe things about your application
that you did not observe before.
Tip 12. Finally, take pride
in the bugs reported by you. Feel free to mention an interesting bug that you
found to a team member.
