• info@helpingtesters.com
  • helpingtesters

Software Testing Interview Questions – 1

October 3, 2017 Manual QA Interview Prep
Software Testing Interview, Software Testing Interview Guide, QA Interview Guide

In Software Testing Interview Questions, questions are just not asked on the terminologies, approaches, and differences. Software Testing Interview Questions on understanding the testing activities, responsibilities of testers for different activities will also be asked. Below are the Software Testing Interview Questions which helps in understanding different activities, the responsibility of testers, and common validation points 

70+ Software Testing Terms and Common Terminologies

QA Life Cycles and Software Testing Approaches

Differences between Terms in Software Testing

Interview Questions for Software Testers – 1

Interview Questions for Software Testers – 2

Interview Questions for QA Test Lead Position

1. What are the attributes of good tester?

Apart from testing an application, any tester should have the below attributes to qualify as a good tester:

  • Analytical, technical, logical skills
  • Ability to apply learnings and knowledge wherever required
  • Detail oriented
  • Having eye-to-detail
  • Good approach under any circumstances
  • Process oriented
  • Constructive destruction
  • Not to make any assumptions. Should ask questions on any unclear points in a professional manner (even if it is a simple thing, it’s better to ask instead of making assumptions on the own)
  • Quality reporting

2. What does constructive destruction actually mean for a tester?

Constructive destruction is a must-have attribute for any tester. From the testing point of view, it means to break the application under test to increase its quality. But when it comes to tester’s psychology, it’s all about reporting negative things in a positive way, so that the team environment is not affected or altered badly.

3. What are the qualities of Software Requirements Specifications document?

Qualitative Software Requirements Specifications document (SRS) should be as below:

  • Clear, Correct, Complete
  • Each requirement should be unique
  • Any dependencies should be highlighted
  • Supporting data or data type should be well-defined
  • Logics should be described
  • External systems, third-party applications should be mentioned
  • Scope should be clear
  • Functional requirements should be covered to the max possible
  • It should be easy to capture testable and non-testable requirements from the SRS document

4. How do the requirements emerge?

Requirements for any application emerge in different ways. It could be from any of the below ways:

  • Customer’s customer’s requirements/business needs
  • Deferred bugs whose fix may affect other features of the application
  • Enhancements – usually called Change requests (CR)
  • Market study for similar competitive products

5. Who designs and reviews Software Requirements Specifications document?

Business Analysts or Customer’s designs Software Requirements Specifications document. Usually, Business Analysts reviews them. If there needs any modification to the document, then upon discussion and mutual agreement between the customer and Business Analysts, SRS will be updated.

6. What are the components of query log?

The query log is the document which contains queries on the requirements which are not clear, ambiguous, missing, and requires more information. This document usually consists of following components:

  • Query Number
  • Requirement / Use case / Wireframe reference number
  • Feature
  • Summary of the query
  • Description on what needs to be answered
  • Logged date
  • Customer’s input for query
  • Status to indicate whether the query is cleared or not (Complete – query is answered and satisfied, Pending – Customer has to still provide answer to the query)

This log is usually maintained by the testing team and is shared within the project.

7. What could be supporting documents for Software Requirements Specifications document?

Software Requirements Specification document can be supported by other documents as well. They are as below:

  • Use Case – This captures required scenarios that are more of real-time and business critical
  • Wireframes – This captures the design of the screens, actual error messages, actual information messages, button names, field names, etc. It gives a visual idea of how the application may look
  • Data Matrix – This captures all possible data and its type supported for each and every field in all the screens across the application. Any limitations and conditions on the fields are well described along with its logic with other fields or expected output

8. What is the ideal timeframe to respond to customer queries? (Important Software Testing Interview Questions)

Any queries from customers should be answered at high priority and immediately. Maximum timeframe accepted to respond to customer queries is 24 hours. This has to be usually answered by the member to whom it is intended. But in case of delays, Managers or Leads can answer on behalf of the member.

9. Who is responsible to design and maintain test plan?  (Important Software Testing Interview Questions)

Test Plan has to be designed and maintained by Test Lead / Test Manager. Test Plan has to be written in the Organization provided template only. But the components of it should match the standards. It is reviewed by Project Manager and Customers, and any comments provided has to be incorporated to keep the Test Plan Complete.

10. Can a project have multiple test strategy documents?

No. Only one Test Strategy document should be designed and it should be at the account level. An account can have multiple projects, but only one test strategy for the entire account.

11. Can a project have multiple test plan documents?

Yes. An account can have multiple projects (Example: Release projects, Maintenance Projects, Proof of Concepts, etc.) and each project can have their own Test Plan.

12. What are the qualities of a good test case?  (Important Software Testing Interview Questions)

Any test case is considered as qualitative only when it meets below criteria:

  • Complete, Correct, Clear
  • Well described on what has to be done
  • Valid
  • Reliable
  • Easy to understand by anyone and is executable
  • Adaptable – when there are enhancements, test case should require only minimum changes
  • No Ambiguity
  • Traceable back to requirements / use cases / wireframes / data matrix

13. Why is reverse traceability matrix important?  (Important Software Testing Interview Questions)

Reverse Traceability matrix plays a vital role in calculating test coverage for the requirements. This is to ensure that all the testable requirements are converted to test cases and all the possible validations for each requirement is captured.

14. How should be the input data matrix design? Who designs it? 

Input data matrix design should capture all the input fields in all the screens across the application. For each and every field it is very important to cover its type, limitations, range, conditions, logic. Also, any dependencies for the fields should be clearly mentioned. If possible each and every field should be supported with examples.

15. How many test cycles can a release have?

A release can have any number of test cycles. The number is decided based on below conditions:

  • Deadlines
  • Complexity of the application
  • Impact of changes – If the changes to features/addition of feature/deletion of the feature are affecting the application very badly, then the number of test cycles will usually be more. In case of minor changes, it will be very less and usually, 2 to 4 cycles will be expected.

 16. How is the test case selected for execution in the test cycle?

Test Case selection for execution in the test cycle depends on the changes/addition/deletion of the feature being done.

  • If the new feature is being added: Test cases of new feature and test cases of associated features are selected
  • If the feature is being modified: Test cases of modified feature and test cases of associated features are selected
  • If the feature is being dropped: Only the associated feature’s test cases are selected

17. Can a test case be passed even if there is a minor bug which does not affect functionality?  (Important Software Testing Interview Questions)

Yes. Test Case can be passed even if it has a minor bug which does not affect functionality. But this has to be one of the known bugs / has to be discussed with leads or managers to pass the test case and also log the bug. This has to be mentioned in the status report and all the stakeholders should be kept informed.

18. How to test input field which is a text box?

Any text box can be tested for the below conditions:

  • Type of the data it supports (Example: If it accepts only English alphabets, provide alphabets only, digits only, special characters only, foreign languages only (take Google translator help), combination of all possible types)
  • Maximum Length (Example: If it has maximum length set to 50 characters, provide more than 50 characters – here it should either accept and display error message upon submission or should not accept typing more than 50 characters)
  • Mandatory checks

19. How to test input field which is a dropdown?

Any dropdown can be tested for the below conditions:

  • Options in available and its selection
  • If the drop-down is for single option selection, it should allow a user to select only one option at any point of time.
  • If the drop-down is for multiple options selection (usually called multi-select drop-down), it should allow user to select multiple options by pressing CTRL key on the keyboard
  • Mandatory checks
  • Default option is configured

20. How to test input field which is a text area?

Any text area (usually this is used for description fields) can be tested for the below conditions:

  • It should accept alphabets, digits, special characters, foreign languages – in general
  • Maximum Length (Example: If it has maximum length set to 100 characters, provide more than 100 characters – here it should either accept and display error message upon submission or should not accept typing more than 100 characters)
  • Pressing Enter key should add new line in the text area instead of submission
  • Mandatory checks (Example: For product descriptions, text area will be mandatory field)

 21. How to test input field which is a radio button?

Any radio button can be tested for the below conditions:

  • Single option selection. At any point of time, multiple options should not be allowed for selection
  • Mandatory checks
  • Default option selected when page is loaded

22. How to test input field which is a checkbox?

Any checkbox can be tested for the below conditions:

  • Single or Multiple options can be selected
  • Mandatory checks
  • Default option selected when page is loaded

23. Mention key points to be followed while logging a bug.

While logging the bug, below key points should be followed:

  • Summary should be short and give the clear idea on what the bug is all about
  • Steps to reproduce should have the complete flow starting from launching the application till bug encountered
  • Severity should be analyzed and provided correctly
  • Component/feature should be selected appropriately
  • OS, browser should be selected with proper versions
  • All the input data should be provided
  • URL of the page where bug is encountered
  • Screenshot should be highlighted indicating where the bug is on the screen
  • Video should be clearly shown covering the entire flow

24. Apart from the application, what are the other possible components to be tested in any project?

The interface between different components should always be tested.

  • Application to database changes
  • Server configuration changes affecting application
  • Interface between Database, Application, Server
  • Request response APIs in the application

These testing should always be carried out by specialized testers.

25. Is it possible to complete entire regression suite for each release?  (Important Software Testing Interview Questions)

When the release date for the application is far enough and the effort required to execute entire regression suite is well adaptable within the timelines, then the entire regression suite execution can be completed with enough resources. But, if the schedule is tight, then it is not possible to execute entire regression suite and it is preferred to automate the regression test cases.

26. How is the feature selected for automation?  (Important Software Testing Interview Questions)

Any feature that is stable and almost working correctly (more than 95%), then it can be considered for automation. If the feature is undergoing modifications, then it cannot be considered for automation until it is stable.

27. In general, what are the areas that cannot be automated in any of the applications?

Areas like actual email verification, printing, third-party tools/plug-ins, navigating to third-party applications cannot be automated.

28. How does the test cycle conclude?

Test Cycle concludes when:

  • All the regression test cases are executed
  • All the identified bugs in the cycle are logged
  • All the bugs fixed are verified and closed
  • There is a proper sign-off from Test Lead / Manager / BAs / Customer

29. Who is responsible to send a Daily status report?

Test Lead is responsible for sending daily status report to all the stakeholders of the project – Test Manager, Business Analysts, Customers

30. What is the mode of communication for Daily status reports?

Email is the proper mode of communication for daily status reports.

About the author

Nandini KS editor

Hello, this is Nandini.

Leave a Reply

Your email address will not be published.