This time we continue the Q&A series of tips and tricks. If you are a software tester or a QA engineer then you must be thinking every minute about finding a bug in an application. And you should be. We will focus on trying to find out the hidden bugs in the system that might occur for special conditions and cause strong impact on the system. You can find such bugs with some tips and tricks.

Tip #1

Understand the whole application or module in depth before you start testing. This will help you immensly and will save you time with navigation during testing. This is a very important step and one that can cost you a lot of valuable time if you do not prepare before you start.

Tip #2

Prepare good test cases before start. This is the next logical step in the process. After you familiarize yourself with the application or page you’re testing, you should think about some test cases. These will come useful later if you need to create testcases for automatic testing, which once more saves time.

Tip #3

Create a sufficient test data before testing. This data set includes the test case conditions and also the database records if you are going to test DB related application.

Tip #4

Perform repeated tests with different test environment. These could include different browsers and system combinations. Depending on your task there could change, but most of the time you will always have to perform tests at least on 2 different browsers so you don’t miss any of the issues.

Tip #5

Try to find out the results patterns and then compare your results with those patterns.

Tip #6

When you think that you have completed most of the test conditions and when you think you are tired somewhat then do some monkey testing. This means try random things for a few minutes, click everywhere, drag any icon you can onto other parts of the application etc. This helps you make a mental break, but you would be surprised just how many bugs can be found by these “impossible” testing situations.

Tip #7

Use your previous test data pattern to analyse the current set of tests.

Tip #8

Try some standard test cases for which you found the bugs in some different application. For example, if you are testing the input text box, try inserting some html tags as the inputs and check the output on display page.

Tip #9

The last tip is simple. Try very hard to find a bug. It will get easier with time and practice, but determination is a key thing to successful testing.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>