Software Testing Interview Questions You'll Most Likely Be Asked

5 of 5 Stars!

Price: $19.95


Software Testing Interview Questions You'll Most Likely Be Asked is a perfect companion to stand ahead above the rest in today’s competitive job market. Rather than going through comprehensive, textbook-sized reference guides, this book includes only the information required immediately for job search to build an IT career. This book puts the interviewee in the driver's seat and helps them steer their way to impress the interviewer.

Table of Contents

1. SDLC and STLC
2. Testing and Methods of Testing
3. Levels of Testing
4. Types of Testing
5. Testing Models or Process
6. Testing Domains
7. Testing Tools
8. Project Management in Testing
9. Testing Industries
10. Standards of Testing
11. Devices Testing
12. Metrics and Measures
13. HR Questions
14. Index


a) 300 Software Testing Interview Questions, Answers and proven strategies for getting hired as an IT professional

b) Dozens of examples to respond to interview questions

c) 77 HR Questions with Answers and proven strategies to give specific, impressive, answers that help nail the interviews

d) 2 Aptitude Tests download available on

Sample from the book

(Below Questions and Answers are randomly taken from different pages of the book)

71: What is globalization testing?


The market today is competitive; clients from all over the world are spreading globally with technology.

This means an application needs to have global settings like functionality, view ability in cross-browsers, view ability in multiple platforms and readability. By using all possible international inputs, Globalization testing checks for proper functionality of the product with respect to culture or locale settings.

Globalization testing is checking for codes to handle international support without violating functionality in a way not to lose data or display problems. The input should accept all the language texts.  The application is first localized & then tested for locale timings and settings, language, content, and interoperability. Some of the steps to follow for testing are:

a) Deciding the priority of each module

b) Selecting a Test platform

c) Creating the test environment

d) Executing test cases

e) Recognizing the problems and correcting them as required.

The important testing types that are involved are acceptability, compatibility, usability, reliability apart from functionality. These tests, check whether the application is ready for worldwide users.

This testing is also known as Internationalization testing.


72: What is alpha and beta stage testing?


Alpha and Beta testing stages are an essential mechanism of the overall software testing process to ensure that the software is free of faults and bugs.

a) Alpha stage testing is the first stage of software testing after the development is done. The term ‘Alpha’ identifies the stage at which the testing is performed in the testing life cycle and is not yet ready for deployment. The testing is done to perform verification purpose and user acceptance testing. The goal is to check, if the project meets requirement specifications.

It is performed by developers at the development site in a virtual environment. It may sometimes be performed independently by Testers. Alpha stage means, testing performed on application or project within the organization. The real end users are absent in this testing. This is pre deployment phase testing. It is both White box and black box testing categories.

b) Beta stage testing is done when software passes the Alpha stage testing. Here, a software product is tested rather than the project or application. The term ‘Beta’ identifies that the product has come to the final deployment stage and is ready to use by the end users.

The testing is performed by end users at their own locations or site by using customer data. The people who are involved in this stage of testing are Test manager/head or Sales Head or Client, End user and/or, Product team. This testing is also the form of Acceptance testing and is always performed outside the organization. The environment in which the testing is performed is known as real time environment or production environment. Beta testing is open to the market and the public and therefore is also called as field testing. This is only a black box testing category.


73: Is there any difference between retesting and regression?



a) Retesting is done to ensure test cases that produced defects in the last execution are fixed and is passed.

b) Retesting is carried out when a defect is fixed.

c) Retesting is done for the test cases which failed earlier in older build.

d) Retesting test cases cannot be prepared before test execution of older fixed defects. Therefore, there is no specific document followed.

e) Retesting has a defect verification process.

f) Automation is not possible for the test cases under Retesting, because only fixed defects are tested. Hence automation cannot be considered.

g) Retesting is prioritized over Regression testing, so defects fixed are tested out before regression testing.

Regression Testing:

a) Regression testing is done to ensure when changes like defect fixes, enhancements to the module or application, updating additional features, do not affect the whole application or product. That is the unchanged portion of the application is not affected.

b) Regression testing is carried out as planned for the specific area or complete testing.

c) Regression testing can be done for test cases which passed earlier in older build.

d) Regression test cases are derived from the user manuals, the functional specification documents, defect reports and tutorials in relation to corrected problems.

e) Regression testing does not have a defect verification process.

f) Automation is possible and is the right time for regression testing.

g) Regression testing that is carried out manually, will be expensive with each new release and is time consuming. Hence automation can be opted when the system is considered stable.

h) Regression testing can be carried out in parallel with Retesting depending upon the availability of the resources.


74: What is a checklist? How is it part of Quality?


Every industry employs QA or QC or Quality management as per the industry standards. The checklist is a part of the quality checking process. A checklist in general term means a list of items to check for existence and coverage in a step by step procedure. It contains ‘To Do and Not to Do’ inspection items to be checked.  A Checklist can be called as a tool for measuring quality performance. This kind of a checklist is widely used for many business projects. A Checklist can be created or designed for almost any process, small or big. It ensures there is nothing missing out from the system. This is a necessary portion to ensure a smooth process and quality delivery to the client. In Software testing, checklist can be created at various stages.

a) Checking scripts assigned

This is always the first step to follow. Scripts are assigned to testers based on the daily workload or based on understanding skills.

b) Checking Test report tool for status of the defect

This is the next important step for the checklist. A Bug report tool is used to keep track of the status of bugs assigned, work in progress and fixed by the developer. The Tester then re-tests and closes the bug to see that the bug is successfully resolved.

c) Checklist is written for executing scripts

Test cases written in a Test template are executed and actual results are entered and then compared and prioritized.

d) Checklist is written for logging defects

Defects are logged with the help of a tool. Developers fix the defects and assigned them to testers for retesting. Resolved defects are closed.

An email is sent to the Team lead with the daily work status report, as per the above checklists for various stages. The report should contain, No. of scripts executed, No. of defects raised, Comments added on defects and queries.

automated software testing, interview skills, interview techniques, interviewing for a job, interviewing success, interviews, it job interview questions, manual software testing, software testing, software testing interview


COM051330-Computers / Software Development & Engineering / Quality Assurance & Testing