CLIENT/MANAGER Level Interview Questions – Part - I

1. What will you do if bug is found in production?

2. What type of challenges you faced working as tester?

3. Tell me about the time when you help you colleague?

4. Two scenarios where you were stuck and how did you solved it?

5. Why did you miss your deadline?

6. How will you handle the situation, if there is difference of opinion with senior?

7. How will you start testing of requirements are not clear?

8. What will you do, if developer is not accepting the bug?

9. If we give you only manual work will you join?

Or Why do you want to switch from automation to Manual?

10. Do you have any question for us?

1. What will you do if a bug is found in production?

- We have to inform our stakeholders (Dev, BA, Product owner, PM)

- Create a Jira ticket

- Do RCA [Root Cause Analysis]

- Check earlier documentation like stories/defects related to current defect

- Start with the fix

- Do impact analysis, how many sub capabilities will be affected

2. What type of challenges have you faced in your career working as tester?

- So it all depends on you experience and what you have worked on.

- Like a person who is working on manual and want to shift to Automation - it is

challenging to understand framework

- Or to implement database automation , jdbc connections implementation

3. Tell me about the time when you help you colleague?

- Here you can give examples of a person who have newly joined and you helped him
 understand the framework you have given KT.

- Or your colleague is stuck in a defect and you helped resolve /retest that bug.

4. Two scenarios where you were stuck and how did you solve it?

- These again depends on your experience, what are the situations you have faced

- Here you can mentioned about production bug or UAT bug and your interaction with client

5. Why did you miss your deadline?

- This is very common scenario, where you have committed for a deadline and you missed it

- It may happen because of following reasons

+ Build was not ready

+ Large set of test cases were there to test

+ You found multiple bug in build

6. How will you handle the situation, if there is a difference of opinion with seniors?

- It may happen that your senior (Lead/BA) does not agree with your testing/opinion

- You need to have proper documentation and logical explanation

- Talk about your findings

7. How will you start testing of requirements are not clear?

- Some time it happens when you join any new team

- You can talk to people who have worked on that project, or have some knowledge about

what they have done till now

- Check for any old documents related to project

- if application is available do Ad-hoc testing

8. What will you do, if developer is not accepting the bug?

- It may happen because dev test in different env and tester test in diff env

- You need to have proper documentation about the defect

- you can connect with Dev separately and explain him

- You can address this issue in Scrum call/ defect triage call

9. If we give you only manual work will you join?

Or Why do you want to switch from automation to Manual?

- This happens when you are applying for manual testing role
 - You can say like, manual testing gives us proper understanding of the functional requirement, which is
necessary to implement automation

- And though for now the role is for manual testing, in future if required i will be able to implement
automation also.

10. Do you have any question for us?

- Never say " No, i don’t have any questions."

- If you get this opportunity, ask about the project for which they are hiring

- Ask about role and responsibilities if you get hired

And finally, you can end up like " It was a great discussion, nice talking to you, have a great time. Thank you.

CLIENT/MANAGER Level Interview Questions – Part - II

Q.11 How will you plan your test or testing?

Q.12 Which fields did you see in test plan?

Q.13 How will you decide your testing is over?

Q.14 If we update a module or functionality, then is it needed to check all the functionalities or you will just check he
particular functionality?

Q.15 You know that your model will release in 6 months, then how will you plan regression testing for the same?

Q.16 What is test coverage?

Q.17 How will you decide when to automate the test cases and why?

Q.18 How to create the test plan?

Q.19 How to create test strategies?

Q.20 How many test cases do you write in a day?

Q.21 How many test cases do you execute in a day?

Q.22 Explain your team size?

Q.23 Do you involve in scrum call and your contribution in that?

Q.11 How will you plan your test or testing?

Answer: This question is about Test planning or how will you create your test plan?

A Test Plan is a detailed document that includes the test strategies, objectives, schedule, estimations, deadlines, and
resources required to complete that project.

We need to focus on some points while creating a test plan, and those are:

+ Analyse the product:

● Who will use the website? What is it used for? How will it work?

+ Design the Test Strategy:

● The project’s testing objectives and the means to achieve them

● Determines testing effort and costs

+ Define the Test Objectives:

This phase defines the goals and expected results of test execution. Since all testing intends to identify as many
defects as possible, the objects must include:

● A list of all software features – functionality, GUI, performance standards- must be tested.
● The ideal result or benchmark for every aspect of the software that needs testing. This is the benchmark to
which all actual results will be compared.

+ Define Test Criteria:

-Entry and Exit criteria, Suspension and re-assumption criteria

+ Resource Planning:

This phase creates a detailed breakdown of all resources required for project completion. Resources include
human effort, equipment, and all infrastructure needed for accurate and comprehensive testing.

+ Plan Test Environment:

A testing environment is a setup of software and hardware on which the testing team is going to execute test
cases.

+ Schedule & Estimation:

Making schedule is a common term in project management. By creating a solid schedule in the Test Planning,
the Test Manager can use it as tool for monitoring the project progress, control the cost overruns.

+ Determine Test Deliverables:

Test deliverables are provided before testing phase Test deliverables are provided during the testing

Test plans document Test Scripts

Test cases documents Simulators
Test design specification Test Data
Test Traceability Matrix
Error logs and execution logs
Q.12 Which fields did you see in test plan?

Answer: Test plan is consisting of Test Strategy, Test Objectives, Testing scope, Level of testing, Entry Exit criteria,
Suspension and re-assumption criteria, Resource planning, Estimation, Test deliverables, Test requirements, defect
management etc.

Q.13 How will you decide your testing is over?

Answer: We have to focus on following points

+ No High priority, High severity defects are open**

+ All critical functionalities are tested

+ All critical test cases are executed and passed

+ Test deliverables are ready e.g Test Summary report, Defect summary report, Closure reports, Test Plan etc.

Q.14 If we update a module or functionality, then is it needed to check all the functionalities or you will just check he
particular functionality?

Answer: Whenever there is change/update in functionality or module, we need to check its effect on other
functionalities. So here we will perform Regression Testing, by doing this we will ensure that all other critical
functionalities are working fine and new code change has no effect on them.

Q.15 You know that your model will release in 6 months, then how will you plan regression testing for the same?

Answer: If the model needs to be released in 6 months, we need to consider following points to plan regression

+ Tester will figure our what are the critical functionalities and related test cases, and will prepare a suit.

+ Whenever there is a code change, this suit needs to be executed and results needs to be verified.

+ Whenever the build is moving from one environment to another environment, regression suit needs to be executed
and result needs to be verified.

+ We need have to fix a timeline, after which the regression suit will be executed like after a sprint end or in a month,
as per requirement.
Q.16 What is test coverage?

Answer: Test coverage is defined as a metric in Software Testing that measures the amount of testing performed by a
set of test. It will include gathering information about which parts of a program are executed when running the test
suite to determine which branches of conditional statements have been taken.

Q.17 How will you decide when to automate the test cases and why?

Answer: A test case should be automated if the following criteria for automation testing apply:
● The task is going to be repeated.
● It’s going to save time.
● The requirements, the test, or the task are low risk, stable, and unlikely to change often.
● The test is subject to human error.
● The test is time consuming.
● The test has significant downtime between steps.
● The test is repetitive.

Q.18 How to create test strategies?

Answer: When writing a test strategy, the following aspects should be considered:

1. Testing objectives.
2. Testing guidelines.
3. Testing approach.
4. Roles and responsibilities.
5. Levels of testing.
6. Test requirements.
7. Test deliverable.
8. Entry and exit criteria.

Q.19 How many test cases do you write in a day?

Answer: Well, it all depends on the functional requirement or feature you are working on, and also the methodology
you are using. For example, in Agile, the no of test cases you write will be less compared to waterfall. On an average
you may write around 5-20 test cases for a User Story [ It’s not a correct no and may differ according to requirement].
For automation you may create 2-3 test scripts in a day.

Q.20 How many test cases do you execute in a day?

Answer: Based on the time availability and in which phase of testing you are in, we will execute the test cases and
pass. This case doesn’t have any standard answer but on an average 5-10 test cases we can execute manually.

Q.21 Explain your team size?

Answer: Here you need to talk about your team, which will be consist of your team lead and other testers. You need
to mention about what different types of testing is performed by your team like UI testing, API testing, DB testing,
Automation etc.

Q.22 Do you involve in scrum call and your contribution in that?

Answer: Yes, as a tester we are part of scrum call, where we give update on our current work allocation. As a part of
our contribution, we can talk about the suggestion we have given in the call like the suggestion to improve testing
process or suggestion to improve communication between dev team and testing team.