Sometime back, I was searching for “Software Testing Tips”, “How to become a smart software Tester”, “Tips for Software Testers”, etc on Google.com.
I come across various websites and in most of the websites, I got these tips – “Have a good test plan”, “Learn & Improve Your Skills”, “Understand the product”, “Write clear, descriptive, unambiguous bug report”. BULLSHIT. These are required skills of a software tester.
So here is my Part 1 of “Practical Software Testing Tips to become a Smart Software Tester.”
Tip 1: Make sure that you clear all your doubts during requirement analysis. Always Ask Yourself “What If..?” (Read How to Review and analyze Software Requirements)
Tip 2: Before the developers deliver the code, have a discussion with them on the functionality/Business rules you have covered in the test cases. Ask them what addition rules they are covering in the code, how the UI will look. This discussion is very required if you want to reduce the QE / Dev conflicts and rework time during test case execution. In case you get conflicts, get it resolved from requirement owner.
Tip 3: Think technically – Try to understand how the application will be designed. Think and ask the developers/DBAs:
What will be the db design?
Any part of code is being reused in multiple places?
Tip 4: Before you report any defect/bug, Are you discussing/confirming it with Developers? If YES, then you are wasting your time. STOP DOING THIS. Be confident and Report defects promptly.
Tip 5: Whenever you got a new feature to test, do a 15¬20 minute high level test to make sure that newly implemented feature is stable. In case you encounter any blocker issue, send a high priority email to the Dev/QE group saying this need to be fixed on priority.
Tip 6: Before you start Test Case Execution, prioritize your test scenarios. For example ¬ scenarios related to Business rules can be of high priority and need to be tested on Priority. Usability or negative testing scenarios can be tested after that. [This is just an example, testers need to decide based on the scope of testing].
Watch less that 3 minute interactive Video:
Stay Tuned for part 2.
– Happy Testing