Testing The Normal Way is Not Enough

i) Do Not Leave Bugs to QA

While writing unit tests and doing it as early as possible. We all know it’s much cheaper to fix the early bugs found. We should not leave bugs to QA department.

ii) Test at First.

Start testing when you have something to test. Tester should start analyzing and testing the application in the starting stage itself, the better we (the testers) understand the product, the better it will be tested. Ideally, developers and testers should discuss how the entire functionality can be tested what can be left to the unit tests, what should be automated via functionality tests as well as prioritize the regression, load, performance, stress, etc. How it is going to satisfy the customers need

iii) Automating Everything is a Risk Process

A man with a tool is a fool. Tester should think out of the box for testing the application. The automation almost always helps in regression. However, it has its own cost as well, so instead of throwing yourself in test automation immediately, first analyze the test value. Is this a simple and common case you’d like to cover? If so, consider integrating it into the unit tests suite. Or If it is complex try to reduce automation for the test case.

iv) Don’t Forget to Test Manually!

Donot forget to test manually. If u are using any tool for automation may produce unknown defects. Automation test cases will verify only the expected test. Don’t forget your automated tests would most probably catch the bugs they are supposed to catch! After all, the human brain can’t be substituted, or at least that wouldn’t be cheap.

You have some ideas on testing a specific feature more, but there are other coming tasks? Write it and implement in some your application. Or probably you are out of ideas about additional testing of this feature? Take the developer who has worked on that for a couple of minutes, discuss how the feature has been tested so far, look at the related unit tests together and go to the next one if you both agree this is ready to go.

v) Product is Completely Tested! It is not True

100% bug free product is not possible.   Developers may mention this is our product this supposed to work in this functionality; this application needs to do this functionality. After the release of the product, In real time product may not full fill the customers need. At last customer may report the product is bug. Product doesn’t seem to be well tested!

vi) Test Never Ends!

Furthermore, regularly get back to think of improving what you’ve done till now.

Just passing the test cases is not covers the entire application has been tested. If u found any bugs in time it needs to be reported to dev team and its needs to be solved immediately. Bugs need to be reduced every moment. Minor bugs may cause the entire application in danger. Whenever a minor bug is resolved then the product should not cause some other defects.

A good tester is always a good analyzer. - Jegan

Negative thinking is necessary for a good software tester. –Jegan