What’s the difference between a professional QA and a mid-level one. In my experience, people often think of software tester as a role only to have enough count of bugs. There is a common conviction that we are “negative” thinkers, that we always complain and we like to break stuff. Don’t follow this way. Now I am working in “Develandoo” and we have released very complicated projects with high quality.I have never had the idea to report the bug as soon as possible. That’s the very wrong way if you want to succeed both in professional scope and in team working. Be only friend and a colleague with each team member and have only one goal to have a quality and reach the success. How do you learn to test your product? To be a professional QA you must have: Technical thinking Practical Thinking Critical thinking Creativity And what is important: communication skills Testing is one of the major phase in Software Development Life Cycle (SDLC). Imagine, you are working as a QA engineer in a software company and a client trusted your company to develop a simple desktop like “Hello World” app. Here your job is to test the app. So let’s go !
Step 1: Requirement Analysis Analyzing and understanding the user requirements is a major part for a Tester job. You have to keep in that mind, your test coverage highly depends on your understanding about the requirements. If you misunderstand any requirements then you may fail to provide test coverage for that part. For example, in the above mentioned scenario we saw that your client asked to develop a desktop based app. But do you know in which platform (Windows, Mac, Linux, etc.) it will run? Let’s just forget that, because your company has Requirement Analyst (small software firms don’t have any actually). Also forget about that, the developers will provide you these information. So if you forget to ask that question, then your test coverage will missing the cross platform testing. Some basic questions may be invoked for understanding the requirements:
- Should it support cross platform?
- What should be the size of the window, color of the text and so on.
Step 2: Determining the Test Plan You have to determine the test plan to write the test cases. When you try to determine the scope, some questions raise again. There are different versions of Operating system. Which OS will support the app and on how many OS you have to test the app.
Step 3: Writing the Test Cases This the most challenging part for a junior tester. Due to the lack of experience, a fresher strive to achieve the standard of test case which will bring out most of the bugs. Different companies support different test case templates. For this reason only few sample title for test cases are I provide here:
- Launch the app
- Verify the UI elements size, color, position…
- Verify the app in different environments
- Verify the design for different resolutions
- Verify validation messages
- So on…
So how to become a professional tester. Make it as a life style. I was always good at breaking things. When the developer will launch the application and everything will work fine after which you will try to launch it and broke everything, then you will realize that you are professional.