Quality Interview Questions and Answers
Question - 41 : - In case you have any doubts regarding your project, how do you approach?
Answer - 41 : -
In case of any doubts, first, try to get it cleared by reading the available artifacts/application help. In case of doubts that persist, ask an immediate supervisor or the senior member of your team.
Business Analysts can also be a good choice to ask doubts. We can also convey our queries with the development team in case of any other doubts. The last option would be to follow up with the manager and finally to the stakeholders.
Question - 42 : - What is the difference between Load and Stress testing?
Answer - 42 : -
Stress Testing is a technique which validates the behavior of the system when it executes under stress. To explain, we reduce the resources and check the behavior of the system. We first understand the upper limit of the system and gradually reduce the resources and check the system behavior.
In Load testing, we validate the system behavior under the expected load. The load can be of concurrent user or resources accessing the system at the same time.
Question - 43 : - What is meant by Verification and Validation?
Answer - 43 : -
Validation is the process of evaluating the final product to check whether the software meets the business needs. The test execution which we do in our day to day life is the validation activity which includes smoke testing, functional testing, regression testing, systems testing, etc.
Verification is a process of evaluating the intermediary work products of a software development lifecycle to check if we are in the correct track of creating the final product.
Question - 44 : - Have you ever managed writing the test cases without having any documents?
Answer - 44 : -
Yes, there are cases when we have a situation where we have to write test cases without having any concrete documents.
In that case, the best way is to:
- Collaborate with the BA and development team.
- Dig into mails which have some information.
- Dig into older test cases/regression suite
- If the feature is new, try to read the wiki pages or help of the application to have an idea
- Sit with the developer and try to understand the changes being made.
- Based on your understanding, identify the test condition and send it to BA or stakeholders to review them.
Answer - 45 : -
The main artifacts used are:
- Functional requirement specification
- Requirement understanding document
- Use Cases
- Wireframes
- User Stories
- Acceptance criteria
- Many a time UAT test cases
Answer - 46 : -
Negative testing is a technique that validates that the system behaves gracefully in case of any invalid inputs. For example, in case the user enters any invalid data in a text box, the system should display a proper message instead of the technical message which the user does not understand.
Negative testing is different from positive testing in a way that positive testing validates that our system works as expected and compares the test results with the expected results.
Most of the time scenarios for negative testing are not mentioned in the functional requirement documents. As a QA we have to identify the negative scenarios and should have provisions to test those.
Question - 47 : - What is the difference between Functional and Non-functional testing?
Answer - 47 : -
Functional testing deals with the functional aspect of the application. This technique tests that the system is behaving as per the requirement and specification. These are directly linked with customer requirements. We validate the test cases against the specified requirement and make the test results as pass or fail accordingly.
Examples include regression, integration, system, smoke, etc
Nonfunctional testing, on the other hand, tests the non-functional aspect of the application. It does not focus on the requirement, but environmental factors like performance, load, and stress. These are not explicitly specified in the requirement but are prescribed in the quality standards. So, as QA we have to make sure that these testing are also given sufficient time and priority.
Question - 48 : - Suppose you find a bug in production, how would you make sure that the same bug is not introduced again?
Answer - 48 : -
The best way is to immediately write a test case for the production defect and include it in the regression suite. This way we ensure that the bug does not get introduced again.
Also, we can think of alternate test cases or similar kinds of test cases and include them in our planned execution.
Question - 49 : - Do you think QA’s can also participate to resolve production issues?
Answer - 49 : -
Definitely!! It would be a good learning curve for QA’s to participate in resolving production issues. Many time production issues could be resolved by clearing the logs or making some registry settings or by restarting the services.
These kinds of environmental issues could be very well fixed by the QA team.
Also, if QA has an insight into resolving the production issues, they may include them while writing the test cases, and this way they can contribute to improve quality and try to minimize the production defects.
Question - 50 : - What would you do if you have a large suite to execute in very less time?
Answer - 50 : -
In case we have less time and have to execute the larger volume of test cases, we should prioritize the test case and execute the high priority test cases first and then move on to the lower priority ones.
This way we can make sure that the important aspects of the software are tested.
Alternatively, we may also seek customer preference that which is the most important function of the software according to them, and we should start testing from those areas and then gradually move to those areas which are of less importance.