• +(91) 8750050183
  • info@helpingtesters.com
  • helpingtesters

Best Questions for Software Testers – Part 2

October 12, 2017 ,
Questions for Software Testers, Software Testing Interview Questions, Interview Guide for Software Testers

This article is the continuation of Popular Questions for Software Testers Part 21. Here Software Testing Interview Questions that mainly focus on how you handle the situations are covered. 


1. How do you handle the situation when the developer does not accept your bug? (Popular Questions for Software Testers)

When your valid bug is not accepted by the developer, then:

  • Explain the bug in detail again to developer
  • Provide references to requirement specification document, test case documents, wireframes, use cases
  • If there is an email communication on the feature which supports the bug, then include that as proof for the bug either by forwarding it to developer or attach it to the bug
  • Discuss your point of view on why you consider the bug as the valid one

 2. Can the build be released to Production when it has open bugs?

Releasing the build depends on few factors on bugs:

  • Build should not have any bugs left open
  • If there are open bugs, then the build release depends on bug’s severity. i.e., if the bug severity is medium or low so that it is not affecting the functionality of the application, then the build can be released.

 3. If the build is released with open bugs, what all has to be taken care? (Popular Questions for Software Testers)

There should be proper communication to all the stakeholders on the open bugs. Also, when the build is signed-off, it should include all the open bugs as a list, for reference. This list has to be released/sent to the support team as a Known-issues list, as they will have to handle any issues raising after releasing to production.

4. How will you decide any issue as a bug or environmental issue?

If the issue is something related to functionality / effecting functionality / not working at all – is decided as the bug.

If the issue is something related to page loading, XML errors, server error messages, slowness, indexing (search engine) – is decided as environmental issue

5. Do you assign bug directly to developer or team lead

Bug logger, usually, has to assign the bug to team lead keeping its status New. Team lead then reviews the bug and assigns it to developer upon opening it.

6. How many test cases can be written in a day?

Writing number of test cases depends on various factors:

  • Proper understanding of requirements
  • Complexity of the feature to which test case is being written
  • Training on the feature – Walkthrough at least for understanding
  • UI cases or functional cases

This question can be answered with the number only when you are in the project and your level of understanding on the project.

7. How many test scenarios can be written in a day?

Writing number of test scenarios depends on various factors:

  • Proper understanding of requirements
  • Complexity of the feature to which test case is being written
  • Connections with other components in the application
  • Training on the feature – Walkthrough at least for understanding

This question can be answered with the number only when you are in the project and your level of understanding on the project.

8. How many test cases or scenarios can be reviewed in a day?

Reviewing a number of test cases depends on the understanding level of the project, expertise in feature (Subject Matter Expertise), UI or functional cases being reviewed, the complexity of the feature, logic involved in cases, verifying traceability provided to requirements.

9. How many bugs can be logged in a day?

A number of bugs that can be logged in a day depending on various factors:

  • Test case/test scenario execution along with bug logging
  • Stability of the application
  • Phase of testing: Usually during ad-hoc testing or initial phase of testing, bug logging rate will be high

This question can be answered with a number only when you are in the project and your level of understanding on the project.

10. How many bugs can be verified in a day?

A number of bugs that can be verified in a day depending on various factors:

  • Other priority tasks over the severity of bugs fixed (If the bug severity is low and there are other priority tasks in your queue, then bug verification can be given low importance. If the bug severity is critical and there are other tasks in your queue, then bug verification can be given high importance)
  • Dependencies to verify the bug (If server has to be brought down, database has to be updated, any batch processing steps are present in bug, then it all has dependencies to be resolved for bug verification)

11. How many test cases can be executed in a day?

Executing a number of test cases depends on various factors:

  • Complexity of the feature for which test case is being executed
  • Level of understanding on the feature – proper training have to be given for this
  • Dependencies during execution (If server has to be brought down then after sometime bring it up, database checks when you don’t have permissions, need confirmation on some point from Business Analyst or Customer, etc.)

This question can be answered with the number only when you are in the project and your level of understanding on the project.

12. How do you plan your day for the tasks?

Once the tasks are assigned, analyze the priority of each task to complete. If there is test case execution, bug verification, response pending to a customer, training to be provided that cannot be skipped, then priority usually goes as below:

  • Responding to customer
  • Bug Verification if bugs are of Critical, Major, Normal severities
  • Test Case execution along with bug logging
  • Training at specified time

 13. How is the task assignment done within the team for execution of test cases?

Task assignment is usually done based on the experience of the testers and priority tasks. Testers with good experience will be assigned tasks that are complex (like complex test cases designing or execution, customer’s bug verification, reporting, etc). Testers with medium or less experience will be assigned simpler or moderate complex level tasks.

14. How do you prioritize your task when both bug verification and test case execution are to be done?

The first priority should always be given for bug verification and then should continue with test case execution.

15. How will you escalate task delays due to dependencies? (Popular Questions for Software Testers)

Task delays due to dependencies will affect the timelines/schedules/plans. These should be escalated very professionally. A clear email on the task delay should be composed and sent to leads/managers, who will then take it forward to concerned team. Email should include:

  • Task that is getting delayed
  • Reason for delay i.e., explain the dependency
  • Affecting tasks due to dependency – execution is on hold, bug cannot be verified, reports cannot be generated, etc.,
  • Request line to clear the dependencies

 16. Who is the coordinator between testing team and customers?

Coordinator between testing team and the customer will be Test Manager. Test Manager should always have complete information about the testing team as well as customer-side actions. All the queries/information from both the sides should be passed on by test manager.

17. If you have to ask something to the customer on anything related to the project, how will you approach? (Popular Questions for Software Testers)

An email is the best mode of communication, keeping your leads, managers in the loop. Precisely explain what you want and also mention the reason for it. It also preferable to include why do you need the information and what tasks have the dependency on your question.

18. Who will record minutes of the meeting?

Minutes of Meeting usually termed as MoM, has to be recorded by leads/managers / any team member who has a strong hold on the project. MoM should include all the discussions (inputs, action items, discussion over any concept) that happen in the meetings. This has to be specifically maintained for meetings with customers/developers/management.

19. What has to be done with minutes of the meeting?

Minutes of the meeting should be shared with the entire testing team.

20. What is the best approach to avoid conflicts with developers? (Popular Questions for Software Testers)

The best approach to avoid conflicts with developers is to have a one-on-one talk with them and come to the general conclusion about issues. Plan for what to discuss, what solution to propose for issues, how to start with the discussion, how to end-up the discussion, etc. Be specific to issues and do not generalize everything during the discussion.

21. Are you a good team player? Justify.

This is a tricky question. This can be answered as Yes, only if you are a:

  • Participate in all the team activities proactively (be it be fun, project related)
  • Attend all the meetings with peers
  • Have a friendly conversation with peers
  • Be one among the team, by joining them in all discussions
  • Do mentorship

22. What will you do when there is not enough time to complete testing? (Popular Questions for Software Testers)

If you don’t have time to complete testing, determine the risky and/or critical features in the project – these features should be error-prone, having bug fixes/updates, developed under high time pressure, has complex business logic, Decide whether to execute test cases for them or to perform thorough ad-hoc testing on them (Adhoc testing might be risky as some validation points may miss-out. For this have a look at test cases and then proceed)

23. How do you train new members in the team?

Providing Training varies from person to person. But still, it is good practice to follow some standards.

  • Plan for the features that you may want to give training.
  • Schedule meeting and invite new members
  • Share all the reference documents of the feature to the new members of the team and ask them to take a look at the document (even if they don’t understand is also fine)
  • Be on time to the meeting, and start the training with short introduction about yourself (like which module you are working for, how long you have been in the project, to whom do you report, etc.)
  • Give an overview of the feature and start with the flow
  • Let the team members ask their questions in between the session, make it interactive and let them try to answer for general kind of scenarios
  • End the session by sharing required credentials for the projects, more information about where they can find information to all their questions (even you should be available for their questions)
  • Ask them to do hands-on and share the queries with you
  • If possible take a quick reverse training from them on later dates (to analyze their level of understanding)

24. How do you give 100% test coverage? (Popular Questions for Software Testers)

Test coverage can be determined by maintaining Reverse Traceability Matrix for test cases and requirements. Here ensure that you design / write test cases for each and every requirements available may be in Software Requirements Specification documents, Wireframes, Data Matrix, or Use Cases.

25. How do you communicate risks?

Risks should always be immediately communicated to the leads/managers either through email, friendly conversation, over messenger, or in the meetings. Let it be dependencies, resource allocation and/or availability, timelines, etc, should be brought to the notice immediately.

26. What are the challenging situations you have faced in testing? (Popular Questions for Software Testers)

Below situations are few where usually testers feel it challenging (pick yours):

  • Tester is new to the domain
  • Changing requirements which need continuous rework on test designs to match current requirements
  • Executing test cases with less knowledge on the feature, and the deadline is very near (may be training was not correctly given, there was no time to understand the feature by doing hands-on, etc.)
  • No proper co-ordination between testers and developers, but you may need to get all the information from them
  • No proper documentation on requirements

27. How do you maintain accountability for day-to-day tasks? (Popular Questions for Software Testers)

Day-to-day tasks should have accountability maintained by individuals. This helps in proving themselves that they are giving their 100% efforts for the tasks. This also helps during appraisals to mention what they have been doing all through until appraisal time. Below are few things which are usually better to be maintained:

  • A number of test cases written/reviewed/updated – with ticket IDs if available and test case names. Here it is also better to track how many test steps are newly written / updated
  • Number of test cases executed – with IDs if available. Here make a note of number of test cases passed, failed, blocked, and number of steps in each test cases
  • Number of bugs logged – with IDs
  • Number of bugs verified and closed – with IDs
  • Number of bugs re-opened – with IDs
  • Number of rejected bugs – with IDs and reason for rejection
  • Trainings, meetings, documentation, and any other tasks performed should have a brief note.

Leave a Reply

Your email address will not be published.

Broaden Your Knowledge. Enroll Today.

Our tutoring services on software testing courses online offer information on a wide variety of courses, ranging from Web Security and Software Testing courses to selenium online training to Mobile Automation Testing. Whatever criterion you need help with concerning advanced technological functions and operations, we’ve got you covered. We also use real world examples and scenarios for solving examples and projects, enhancing your knowledge and broadening your horizon.