***********************************************************************************
Manual QA Lead position Interview Questions and Answers SET-2
***********************************************************************************
21. How do you provide estimations?
Best practices for providing estimations are that:
Add buffer time, so that it helps to deal with delays caused due to any unexpected reasons
Resource planning. Have balanced team with variant experience and skills
Past experience. Use the learnings from your past experience while estimating, assuming possibilities
22. What good practices you can bring in the team?
As a QA lead, there will be opportunities to put the ideas the way wanted. Few things that can be practiced within the team can be:
Add buffer time, so that it helps to deal with delays caused due to any unexpected reasons
Resource planning. Have balanced team with variant experience and skills
Past experience. Use the learnings from your past experience while estimating, assuming possibilities
22. What good practices you can bring in the team?
As a QA lead, there will be opportunities to put the ideas the way wanted. Few things that can be practiced within the team can be:
- Documentation standards
- Review standards
- Metris
- Recognitions
- Teamwork and bonding
- Continuous scope of learning
23. When is the bug in the new state, as a responsibility to open it, what factors you look into?
When the bug has to be Opened and assigned, below factors should be considered by QA Lead:
- Is the bug valid
- Is the bug information complete
- Are all the fields provided correct values
- Is the proper analysis done before logging the bug
- Is the bug duplicate / out-of-scope for the release
- Is it really a bug or environment issue
24. What Are The Steps You Follow To Create A Test Script?
Creating a test script usually requires the below steps.
Step-1# The primary requirement is to get a thorough understanding of the Application Under Test.
To achieve this, we will read the requirements related documents very thoroughly.
In case the requirements document is not available with us, then we will use other available references like the previous version of the application or wire-frames or screenshots.
Step-2# After developing an understanding of the requirements, we will prepare an exhaustive list of the areas to be tested for the AUT. The focus in this step is to identify “What” to test. Thus the outcome of this step is a list of test scenarios.
Step-3# After we are ready with the test scenarios, our focus shifts on “How” to test them. This phase involves writing detailed steps about how to test a particular feature, what data to enter (test data) and what is the expected outcome.
With all this done we are ready for testing.
25. What Are The Key Elements In A Bug Report?
An ideal bug report should contain the following key points.
A unique ID.
Defect description – a short description of the bug.
Steps to reproduce – include the detailed test steps to emulate the issue. We should also provide the test data and the time of its occurrence.
Environment – add any system settings that could help in reproducing the issue.
Module/section of the application in which issue has occurred.
Severity
Screenshots.
Responsible QA – This person is a point of contact in case you want to follow-up regarding this issue.
26. How Will You Overcome The Challenges Due To Unavailability Of Proper Documentation For Testing?
If the standard documents like System Requirement Specification or Feature Description Document are not available then QAs may have to rely on the following references if available.
Screenshots.
A previous version of the application.
Wireframes.
Another reliable method is to have discussions with the developer and business analyst. It helps in closing the doubts and opens a channel for bringing clarity on the requirements. Also, the e-mails exchanged could also be useful as a testing reference.
SMOKE testing is another good option which will help to verify the main functionality of the application. It also reveals some very basic bugs in the application.
If none of these work we can just test the application from our previous experiences.
27. Is There Any Difference Between Quality Assurance, Quality Control, And Software Testing. What Is It?
Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.
Quality Control (QC) is related to the quality of the product. QC not only finds the defects and suggests improvements also. Thus the process that is set by QA is implemented by QC. QC is the responsibility of the testing team.
Software Testing is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed. Thus it helps to maintain the quality of the product to be delivered to the customer.
28. What Is The Best Approach To Start QA In A Project?
A good time to start the QA is from the beginning of the project startup. In this way, the QA team will get enough time to do proper planning for the processes followed during the testing life cycle.
It’ll also ensure that the product to be delivered to the customer satisfies the quality criteria.
QA also play an important role to initiate the communication between the domain teams. The testing phase starts after the test plans are written, reviewed and approved.
26. How Will You Overcome The Challenges Due To Unavailability Of Proper Documentation For Testing?
If the standard documents like System Requirement Specification or Feature Description Document are not available then QAs may have to rely on the following references if available.
Screenshots.
A previous version of the application.
Wireframes.
Another reliable method is to have discussions with the developer and business analyst. It helps in closing the doubts and opens a channel for bringing clarity on the requirements. Also, the e-mails exchanged could also be useful as a testing reference.
SMOKE testing is another good option which will help to verify the main functionality of the application. It also reveals some very basic bugs in the application.
If none of these work we can just test the application from our previous experiences.
27. Is There Any Difference Between Quality Assurance, Quality Control, And Software Testing. What Is It?
Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.
Quality Control (QC) is related to the quality of the product. QC not only finds the defects and suggests improvements also. Thus the process that is set by QA is implemented by QC. QC is the responsibility of the testing team.
Software Testing is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed. Thus it helps to maintain the quality of the product to be delivered to the customer.
28. What Is The Best Approach To Start QA In A Project?
A good time to start the QA is from the beginning of the project startup. In this way, the QA team will get enough time to do proper planning for the processes followed during the testing life cycle.
It’ll also ensure that the product to be delivered to the customer satisfies the quality criteria.
QA also play an important role to initiate the communication between the domain teams. The testing phase starts after the test plans are written, reviewed and approved.
29. Explain The Difference Between Smoke Testing And Sanity Testing?
The main differences between smoke and sanity testing are as follows.
Whenever there is a new build delivered after bug fixing, it has to pass through sanity testing. However, smoke testing is done to check the major functionalities of the application.
Sanity testing is done either by the tester or the developer. However, smoke testing is not necessarily done by a tester or developer.
Smoke tests precede sanity test execution.
Sanity testing touches critical areas of the product to ensure the basics are working fine. However, smoke tests include a set of high priority test cases focussing on a particular functionality.
30. Is There Any Difference Between Retesting And Regression Testing?
The possible differences between Retesting and Regression testing are as follows.
We perform retesting to verify the defect fixes. But the regression testing assures that the bug fix didn’t break other parts of the application.
Also, regression test cases verify the functionality of some or all the modules.
Retesting involves the execution of test cases that are in a failed state. But the regression ensures the re-execution of passed test cases.
Retesting has a higher priority over regression. But in some cases, both get executed in parallel.
The main differences between smoke and sanity testing are as follows.
Whenever there is a new build delivered after bug fixing, it has to pass through sanity testing. However, smoke testing is done to check the major functionalities of the application.
Sanity testing is done either by the tester or the developer. However, smoke testing is not necessarily done by a tester or developer.
Smoke tests precede sanity test execution.
Sanity testing touches critical areas of the product to ensure the basics are working fine. However, smoke tests include a set of high priority test cases focussing on a particular functionality.
30. Is There Any Difference Between Retesting And Regression Testing?
The possible differences between Retesting and Regression testing are as follows.
We perform retesting to verify the defect fixes. But the regression testing assures that the bug fix didn’t break other parts of the application.
Also, regression test cases verify the functionality of some or all the modules.
Retesting involves the execution of test cases that are in a failed state. But the regression ensures the re-execution of passed test cases.
Retesting has a higher priority over regression. But in some cases, both get executed in parallel.
31. What Is The Best Approach To Start QA In A Project?
A good time to start the QA is from the beginning of the project startup. In this way, the QA team will get enough time to do proper planning for the processes followed during the testing life cycle.
It’ll also ensure that the product to be delivered to the customer satisfies the quality criteria.
QA also play an important role to initiate the communication between the domain teams. The testing phase starts after the test plans are written, reviewed and approved.
32. Explain The Difference Between Smoke Testing And Sanity Testing?
A good time to start the QA is from the beginning of the project startup. In this way, the QA team will get enough time to do proper planning for the processes followed during the testing life cycle.
It’ll also ensure that the product to be delivered to the customer satisfies the quality criteria.
QA also play an important role to initiate the communication between the domain teams. The testing phase starts after the test plans are written, reviewed and approved.
32. Explain The Difference Between Smoke Testing And Sanity Testing?
The main differences between smoke and sanity testing are as follows.
Whenever there is a new build delivered after bug fixing, it has to pass through sanity testing. However, smoke testing is done to check the major functionalities of the application.
Sanity testing is done either by the tester or the developer. However, smoke testing is not necessarily done by a tester or developer.
Smoke tests precede sanity test execution.
Sanity testing touches critical areas of the product to ensure the basics are working fine. However, smoke tests include a set of high priority test cases focusing on a particular functionality.
33. Is There Any Difference Between Retesting And Regression Testing?
The possible differences between Retesting and Regression testing are as follows.
We perform retesting to verify the defect fixes. But the regression testing assures that the bug fix didn’t break other parts of the application.
Also, regression test cases verify the functionality of some or all the modules.
Retesting involves the execution of test cases that are in a failed state. But the regression ensures the re-execution of passed test cases.
Retesting has a higher priority over regression. But in some cases, both get executed in parallel.
34. What Are The Severity And Priority Of A Defect? Explain Using An Example.
Priority reflects the urgency of the defect from the business point of view. It indicates – How quickly we need to fix the bug?
Severity reflects the impact of the defect on the functionality of the application. Bugs having a critical impact on the functionality require a quick fix.
Here are examples which show the bugs under different priority and severity combinations.
High Priority And Low Severity.
The display of the company logo is not proper on its website.
High Priority And High Severity.
While making an online purchase, if the user sees a message like “Error in order processing, please try again.” at the time of submitting the payment details.
Low Priority And High Severity.
Suppose we have a typical scenario in which the application crashes, but such a scenario has a rare occurrence.
Low Priority And Low Severity.
These are typo errors in the displayed content like “You have registered success”. Instead of “successfully”, “success” is written.
Whenever there is a new build delivered after bug fixing, it has to pass through sanity testing. However, smoke testing is done to check the major functionalities of the application.
Sanity testing is done either by the tester or the developer. However, smoke testing is not necessarily done by a tester or developer.
Smoke tests precede sanity test execution.
Sanity testing touches critical areas of the product to ensure the basics are working fine. However, smoke tests include a set of high priority test cases focusing on a particular functionality.
33. Is There Any Difference Between Retesting And Regression Testing?
The possible differences between Retesting and Regression testing are as follows.
We perform retesting to verify the defect fixes. But the regression testing assures that the bug fix didn’t break other parts of the application.
Also, regression test cases verify the functionality of some or all the modules.
Retesting involves the execution of test cases that are in a failed state. But the regression ensures the re-execution of passed test cases.
Retesting has a higher priority over regression. But in some cases, both get executed in parallel.
34. What Are The Severity And Priority Of A Defect? Explain Using An Example.
Priority reflects the urgency of the defect from the business point of view. It indicates – How quickly we need to fix the bug?
Severity reflects the impact of the defect on the functionality of the application. Bugs having a critical impact on the functionality require a quick fix.
Here are examples which show the bugs under different priority and severity combinations.
High Priority And Low Severity.
The display of the company logo is not proper on its website.
High Priority And High Severity.
While making an online purchase, if the user sees a message like “Error in order processing, please try again.” at the time of submitting the payment details.
Low Priority And High Severity.
Suppose we have a typical scenario in which the application crashes, but such a scenario has a rare occurrence.
Low Priority And Low Severity.
These are typo errors in the displayed content like “You have registered success”. Instead of “successfully”, “success” is written.
35. What Is The Role Of QA In Project Development?
QA stands for QUALITY ASSURANCE. QA team assures the quality by monitoring the whole development process. QA tracks the outcomes after adjusting the process to meet the expectati
36. As Per Your Understanding, List Down The Key Challenges Of Software Testing?
Following are some of the key challenges of software testing.
Availability of Standard documents to understand the application.
Lack of skilled testers, tools, and training.
Understanding requirements, Domain knowledge, and business user perspective understanding
Agreeing on the Test Plan and the test cases with the customer.
Re-execution efforts due to changing requirements.
The application is stable enough to be tested otherwise retesting efforts become high.
Testers always work under stringent timelines.
Deciding on to which tests to execute first.
Testing the complete application using an optimized number of test cases.
Planning test cases for other stages of testing like Regression, Release, and Performance testing.
37. It’s observed that the testers in your organization are performing tests on the deliverable even after significant defects have been found. This has resulted in unnecessary testing of little value because re-testing needs to be done after defects have been rectified.
You are the test manager and going to update the test plan with recommendations on when to stop testing. List the recommendations you are going to make.
Following steps need to be taken:
a) Acceptance criteria should tighten.
b) Test cases should be re-evaluated (preferably peer review).
c) If possible more test cases should be added. With boundary value and equivalence class partition cases.
d) More test cases with the invalid condition should be added.
e) Stop criteria needs to be modified.
38. Do you write test cases?
The answer always should be a resounding “Yes”. Test leads are testers too.
39. How do you resolve team member issues?
Informally, first. Ask them out for coffee individually and listen to each one’s side of the issue. If it’s a simple misunderstanding, ask them to resolve it within themselves mutually. If need be, call for a meeting and talk to them without letting things escalate. Tolerate until things do not impact work. When they start to cascade and affect project, warn and if necessary, escalate to human resources as a last resort.
40. How do you provide feedback to a team member who isn’t doing very well?
First and foremost, set guidelines for all team members of what is expected of them and in what time frame. In short, define the parameters of success. For example, if it’s a new team member, let them know what you expect from them:
What module they will be working on?
Timelines
Deliverables
Formats of deliverables
Updating/managing work on tools (such as QC, Rally, JIRA, etc.)
Timesheets and so on…
Set a period of time after which to evaluate, such as 30 days or so. Once done, collect statistics-
41. How do you handle induction of new team members? OR What do you do to train new team members?
42. How much is your involvement in reviews of test cases, defects and status reports?
I am involved in the test case reviews just as any other team member is. We do periodic peer reviews. I do not review every one’s work; however we review each other’s work. There are very strict processes established before this process begins so all of us can share work and make sure this goes on smoothly.
All the defects are re-checked by me to make sure they are valid, not duplicates and complete in their description. This is more of a task in the beginning of the test cycles, however as we get more into testing, this step reduces as the teams are more comfortable with the process and can do this effectively. All status reports are consolidated and sent by me as this is a team lead’s job as per the company’s process.
QA stands for QUALITY ASSURANCE. QA team assures the quality by monitoring the whole development process. QA tracks the outcomes after adjusting the process to meet the expectati
- Quality Assurance (QA) does many tasks like the following.
- Responsible for monitoring the process to be carried out during development.
- Plans the processes to follow for the test execution phase.
- Prepares the time-table and agrees on the Quality Assurance plan for the product with the customer.
- Communicates the QA process to other teams and their members.
- Ensures traceability of test cases to requirements.
36. As Per Your Understanding, List Down The Key Challenges Of Software Testing?
Following are some of the key challenges of software testing.
Availability of Standard documents to understand the application.
Lack of skilled testers, tools, and training.
Understanding requirements, Domain knowledge, and business user perspective understanding
Agreeing on the Test Plan and the test cases with the customer.
Re-execution efforts due to changing requirements.
The application is stable enough to be tested otherwise retesting efforts become high.
Testers always work under stringent timelines.
Deciding on to which tests to execute first.
Testing the complete application using an optimized number of test cases.
Planning test cases for other stages of testing like Regression, Release, and Performance testing.
37. It’s observed that the testers in your organization are performing tests on the deliverable even after significant defects have been found. This has resulted in unnecessary testing of little value because re-testing needs to be done after defects have been rectified.
You are the test manager and going to update the test plan with recommendations on when to stop testing. List the recommendations you are going to make.
Following steps need to be taken:
a) Acceptance criteria should tighten.
b) Test cases should be re-evaluated (preferably peer review).
c) If possible more test cases should be added. With boundary value and equivalence class partition cases.
d) More test cases with the invalid condition should be added.
e) Stop criteria needs to be modified.
38. Do you write test cases?
The answer always should be a resounding “Yes”. Test leads are testers too.
39. How do you resolve team member issues?
Informally, first. Ask them out for coffee individually and listen to each one’s side of the issue. If it’s a simple misunderstanding, ask them to resolve it within themselves mutually. If need be, call for a meeting and talk to them without letting things escalate. Tolerate until things do not impact work. When they start to cascade and affect project, warn and if necessary, escalate to human resources as a last resort.
40. How do you provide feedback to a team member who isn’t doing very well?
First and foremost, set guidelines for all team members of what is expected of them and in what time frame. In short, define the parameters of success. For example, if it’s a new team member, let them know what you expect from them:
What module they will be working on?
Timelines
Deliverables
Formats of deliverables
Updating/managing work on tools (such as QC, Rally, JIRA, etc.)
Timesheets and so on…
Set a period of time after which to evaluate, such as 30 days or so. Once done, collect statistics-
41. How do you handle induction of new team members? OR What do you do to train new team members?
- Set aside time for knowledge transfer and orientation
- Share all the information regarding who to get in touch with in case of questions regarding different areas of the system and their email addresses or physical introductions (For example: BA, networking team, tool admins, help desk, Dev team etc.)
- Provide tool accesses
- Share documentation, templates, previous artifacts, test plans, test cases, etc
- Share the expectations in terms of their performance (refer to the answer to questions number: 3)
- When possible, assign a team member to work with them closely for a brief amount of time
- Keep the channels of communication open to stay in touch and understand their progress
42. How much is your involvement in reviews of test cases, defects and status reports?
I am involved in the test case reviews just as any other team member is. We do periodic peer reviews. I do not review every one’s work; however we review each other’s work. There are very strict processes established before this process begins so all of us can share work and make sure this goes on smoothly.
All the defects are re-checked by me to make sure they are valid, not duplicates and complete in their description. This is more of a task in the beginning of the test cycles, however as we get more into testing, this step reduces as the teams are more comfortable with the process and can do this effectively. All status reports are consolidated and sent by me as this is a team lead’s job as per the company’s process.
Wow .. nice explanation.
ReplyDelete