QA Common Interview Questions When Applying for the Position in Quality Assurance Company
Time for your QA interview is approaching, isn’t it? And you are likely preparing for this event: looking for a quality assurance company, choosing appropriate outfit and coming up with answers to the sample interview questions. Below are the few popular questions & answers that might help you pass the job interview successfully.
So, you are welcome to be familiar with the following:
What is the difference between a test case and a test plan? What does each contain?
The test plan document describes the overall testing strategy of a particular project. It includes resources, deliverables, approach, schedule and the scope of testing activities.
The test case is a more specific document laying out test data, testing environment, inputs, scenarios, expected and actual results. It is designed to test a particular software application.
What is a software development lifecycle?
Well, the software development lifecycle is the process wherein software is designed, developed and tested.
What is positive and negative testing?
While testing an app with the valid input data you ensure that it performs as supposed to, so you are running a positive test.
When testing an app with the invalid test data you ensure that it does not perform as supposed to, and, in this case, you are running a negative test.
Providers of software testing services offer professional service solutions to be tailored to your particular environment so as to ensure success of your project/ software scenario.
What a unique key? Primary key? How do the two differ?
A unique key is destined to ensure that there are no 2 duplicate rows in database.
A primary key is another name for a unique key, and it is meant to identify uniqueness of each row in a table.
Primary key must be always unique.
It is not necessary for a unique key to be a primary key.
What are requirements? Specifications? Compare the two.
Requirements are the functions, features and objectives of a certain software system as determined by the customer. They should specify the what, not the how, therefore only needs and expectations are documented in them.
Specifications, on the contrary, describe how to achieve these requirements, and they should specify the how. Specifications contain the idea of how to solve the problem, they provide guidelines for a testing team members for qualification of every technical requirement.
When is it time to carry out functional testing?
As a matter of fact, all esteemed software testing companies start this type of testing early in the development life cycle. The reason for that is that the tests thoroughly check the code ensuring that all components of the app are functioning.