A tests case is not the entire world, you know. Let’s imagine you are testing mobile applications. You have a script and your requirements. You have test cases up and ready along with your trusty tools. But is that really all it takes to perform decent tests? Don’t get my writing wrong, planning is important however it is not something ant tester should primarily rely on.
Just ask yourself if you have tested all you could straight out of that product of yours and were your efforts applicable to the project scope? Did you really do your best to make sure no bug runs free even if it was more your test plan required? If the answer to these questions is a solid ‘yes’ you are probably a great testers and you don’t actually have to read the following part of this post, however if you have doubts just go through the nice advices listed below:
- Do you know the developer or even their team you will be working alongside with? Since when? Form the project start or you just send them a bug report as your first greeting? The best way of nailing a project lies within personal comfort and when job is involved it depends on many factors and social ones as well. If you get comfortable with everybody you will be working together with before testing actually begins things will go much easier for you. And if you are friends with developers you will get all the latest updates from them directly before they even begin writing code for some features. You’ll just have to ask what troubles them and get a straight ‘where to look firs’ answer.
- You are never a one man army. Your fellow testers or your team lead may have an answer to the question you are struggling on for ages now.
- If you currently are waiting for materials that should be tested it does not mean you can kick back and forget about everybody. Staying in touch with the development side is critical or you may be astonished and overwhelmed with recent changes the app under test has gone through from the Architecture perspective, etc.
- Being comfortable with your team is not enough. Are you comfortable with the application under test? Take your time to go through it for as much as necessary before starting your tests. It will work for none other than you in advantage, really.
If you want one, here is a little checklist for nice testers that are great with their jobs. It’s not some kind of a necessity, but positive answers to these following questions do mean you have a better time testing and perhaps are better than several of your colleagues:
- Do you know the developers team? Do they know you?
- Where you ever asked for an opinion about this or that feature from your Project Manager?
- So you are in a shower, are you thinking about breaking a particular feature you were working on?
- Where you ever cheered by developers for finding a really great defect?
- Are you always afraid of a feature release?
If you answer yes to all I’d call it a job well done!