Testing 101

Testing is no Rocket-Science (or at least not always), and you can be a pretty good tester simply by understanding what your company expects from you and how can you contribute to the overall process of developing and releasing your.
For example:
–  Start your process by sitting down with your team an analyzing what parts of the application have the bigger risks and what can all of you do in order to handle these risks
–  Make sure you are clear on what are the most important areas of your product
–  Understand how your users will work with the system once it is released
–  Be in contact with your developersto understand where they are working and what feedback you can give them


Following is a list containing a number of post that may help specially young testers in their initial steps on the testing world:

Personal and professional skills
– What makes a good tester?
– Ask yourself what were you hired to do?
– A good tester asks good questions
– How to survive your job as a start-up tester

Test planning and management
– Master test plan – the strategic side of testing
– The simple difference between product and project risks
– Release criteria – defining up front when the product will be ready to be released
– Functional testing types
– Sanity, regression, smoke, etc. Do we need all these testing types?

Bug reporting and tracking
– Principles of good bug reporting
– What to think of when defining your company’s bug lifecycle
– Severity vs Priority of a bug
– Using a severity look-up table for better and more accurate bug classification


Regardless if you are only getting started in the world of testing, or if you have been working as a tester or test-lead for a number of years, there are always things to learn and aspects where we can improve our testing skills. I believe that by sharing our experiences and challenges with others helps us to learn from one another and also to get feedback that will help each other to improve our testing skills even further.

Shares