Ref http://inderpsingh.blogspot.com/2010/03/how-to-find-more-or-better-bugs-12-tips.html
I copied directly
Well, we know that we don't find all the bugs in the application under test (given that the application at hand are not si Mple). However, we do want to discover and report the most and the best bugs so we can. You need more ideas if you want to find more or better bugs than your do at present. Here is the tips. Go to the video, how to become software testing Expert or read on.
Tip 1.Review the application ' s requirements often. You may notice this no or partial test cases exist for certain requirements. You could find bugs when you test for these requirements. Keep abreast with the change requests/changes to requirements. Be quick and your may find bugs immediately after a requirement change have been first implemented.
Tip 2.It is possible so you have positive test cases only. If So, the create negative test cases for each requirement and execute them.
Tip 3.Execute each test case with a variety of interesting test data (generated for example by the Boundary-value analysis Techn Ique or pair-wise testing technique).
Tip 4.Test the interface of your application with external systems carefully. This is the where a number of bugs may exist.
Tip 5.Another place-to-look-for-bugs is the application-settings (since this was one area, the May are 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/browser s 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 cosmetic bugs. If they would inconvenience a user, they should be reported and fixed.
Tip 9.Create a list of items for the would if you had the time. When you test your application, your may find yourself taking mental notes of things so you would like to test later. Jot these things in your list. Come back to the application another time and test the things in your list against all areas of the application.
Tip Ten.In case you were working as part of a TESTING/QA team, does not restrict yourself to the areas it is supposed to test . You could find bugs in the other areas. This would also has the nice side-effect of increasing your overall knowledge of the application.
Tip one.Instead of rushing through your tests at top speed, slow down (I know it was difficult). You would give yourself time to think more clearly. You would start-to-observe things about your application so you do not observe before.
Tip.Finally, take pride in the bugs reported by you. Feel free to mention an interesting bug, that's found to a team member.
A Word of warning. Don't get carried away if you suddenly start finding a lot more/better bugs. You should still take the time to contemplate each bug, reproduce it, match it to the requirement and carefully create a G Ood Bug report.
Enjoy bug-hunting!POSTED by Inder P-SINGH at 9:22 PM
How to find more or better bugs (tips to explode your bug count and/or severity)?
