The job of a QA tester is not something that comes handy. They are hardworking individuals assigned with difficult tasks on a regular basis.
It is their duty and responsibility to transfer important plans and to go through various test processes for software that has been developed recently in order to make sure that it works according to the first specifications.
The biggest difference between QA analysts and QA testers is that the analysts emphasize on removing mistakes and defects while the testers try to find bugs and diagnose all errors before the product has been released. They do this once more after the release.
This article will give you a brief idea on the sort of questions you should ask while sitting on the other side of the desk. If you are someone who is going to sit for the interview, then make sure you answer all questions in the clearest way possible.
Before you go to attend one, please make sure you have rehearsed some of these questions with a friend. You will surely be helped at the end of this.
1. Tell me something about yourself?
I started off my career as a QA in the year ____. Since then I have worked on several operating systems such as Windows 2000, Windows 95, and Windows XP etc. Testing applications come very handy to me. I have taken care of applications such as Java, Visual basics, CC+ etc. Client server applications and web based applications are also fall under this category.
Being a QA, I also have experience in the field of writing. Test Plans, Test Cases are a few examples. I have also attended several meetings with project managers and business analysts.
When different kinds of testing come into question, I have explored that field as well. Whether it is Smoke Testing, Integration Testing, Regression Testing, Blackbox or UAT Testing, I have given all of them a shot. Writing defects is something other I laid special emphasis on.
I would always assess, reassess, and test them thoroughly before passing it on. If the defects were not fixed, I would make the effort to reopen them again.
2. What do you think is a test plan? Have you written one before? What does it usually consist of?
A test plan is a sort of document which analyzes the resource, scope, approach and schedule of several testing activities. It will help you to find items that need to be tested, its features that need further testing, the risks that come with some and the solutions as well.
Yes I have written a test plan before. It consists of history, contents, introduction, scope, overview and approach. The risks and assumptions are not left out either,
3. Define a Test Case and a Use Case? What do they consist of?
A test case is again a document which gives you a step by step detailed idea on how you can test an application. It usually comprises of results (pass or fail), remarks, steps, outputs and description.
A use case on the other is a document of another kind. It helps you understand the actions of the user and the response of the system found in a particular functionality. It comprises of the cover page, revision, contents, exceptions, and pre and post conditions.
4. What is a test strategy?
A test strategy helps you understand the process of testing in every software development cycle. It has been made in such a way that all project managers and developers will be informed about some of the most important issues of testing. All objectives, methods, total time and the resources which are needed for the project are explained.
A few components you will always find in a test strategy are test level and test schedules, test groups and test priorities, test summary, requirements of the environment, responsibilities etc.
5. Name the different kinds of software testing
The different types of software testing are unit testing, alpha testing, beta testing, shakeout testing, smoke testing, white and black box testing, integration testing, regression testing, load testing, stress testing, black box and white box testing, performance and user acceptance testing.
6. What is SQL?
SQL stands for Structured Query Language. It is an American National Standards Institute computer language which is used for analyzing and assessing the database systems. The statements of SQL are used to get hold of data and retrieve it. They only work with database programs such as MS Access, Informix, Oracle, Sybase.
However there are also different kinds of SQL languages found today. They have to be in compliance with the standards of the ANSI. The keywords should be supported in the same way.
7. Describe Change Control:
Change Control is also popularly known as Change Request. It tells us in details about the additional functionalities which are included once the Business Requirement Document has been signed off.
8. What is a build?
A build is basically a component or a folder that contains one of the modules of the software. This is usually prepared by the Configuration Management Team.
9. Describe the bug life cycle
Bug life cycle basically comprises of numerous statuses of an error during its life cycle. A few examples are open, deferred, solved, reopened, fixed, solved and closed. You may also speak about this process and the way in which you monitor and determine the status with the help of several points.
10. ‘Tell us about the biggest bug you have ever found.
In my writing experience, I have found several defects. Some of them were small whereas some of them were huge. The biggest one I have encountered so far is in the previous project on a page where I found a button called “More Information”.
Once the person using the computer pressed that button, a new window would automatically pop up. I would then close the window by using three ways. First I would click on ‘X’ located on the top right corner of the page.
I would then click on Close button and finally the combination keys on the keyboard.
11. How do you plan on dealing with your team members?
There are higher possibilities that I won’t be the only one in the team. At times dealing with the team members can get very difficult and frustrating. There will be quarrelsome dispositions and misunderstandings and some will also try to ignore the other. But my purpose is to look beyond all of this. We are a team and we should work together to reach a common goal. I will be friendly and invite them over for coffee.
As a human, it is very important to share feelings and have important discussions and that is exactly what I intend to do. This is something that not only me but everyone else in a working environment should apply.
12. Have you used automation tools before?
Yes! I have used defect tracking tools several times such as ClearQuest and TestDirector. (In case you have not used these tools, you may say instead that “I am well aware of these tools. I have conducted a few tests before where these tools were required but I need to go through them once more in order to make a fresh start”)
13. Do you like the QA job? If yes, tell us why?
Yes I do like the QA job. The only reason behind this is because the job is process oriented. This means that here I have the opportunity to do try several things at the time. I can analyze the needed documents, test the application, write test plans and test cases, prepare reports and retest them once again if the need arises. My favorite task would be reducing defects. The more defects I find while working, the happier I will be.
If you are about to sit for an interview and it is your desire to become a QA, then this article will definitely take care of some of the most basic questions that several companies ask.
All important details have been mentioned so that you don’t miss out on a single one. These questions have been asked by interviewers for years and some of them are still popular today. You should also make it a point to practice all your answers right in front of the mirror.
This will boost your confidence and help you nail that interview like a professional. It might seem a little difficult at first, but with a little practice you can do almost anything!