Software Testing Interview Questions with answers – basic questions list pdf

Are you planning to attend a software testing interview soonest? There are several questions you are likely to be asked during the interview. The earlier you know what to anticipate the better the outcome of the interview would be. So, here are the top 30 software testing interview questions you may be asked, as well as their answers.

  1. What is ‘software Testing’?

Software testing is the act of operating a system or application under control and then assessing their results. It is intentionally simulating a problem situation in order to work out a possible remedy in case a situation like that actually happens.

  1. What kind of testing should we consider?

The basic testing to consider include Blackbox testing, Integration testing, Whitebox testing, User acceptance testing, Load testing, Acceptance testing, Performance testing, and Smoke testing.

  1. What is Software ‘quality’?

Quality software is software that is reasonably free from bug, is up to the requirements and/or expectations, delivered on time and according to the budget, and is easy to maintain.

  1. What is ‘Software Quality Assurance’?

Software Quality Assurance also known as Software QA, encompasses the entire process of developing software: observing and improving the process, seeing that the standards and procedures agreed upon are followed, and making sure that problems are discovered and also fixed.

  1. Does every software project need testers?

This solely depends on the context or size of the project, the methodology of development, risks involved, and the experience and skills of the developers. Generally, every project would need testers, except in some cases. A project that is non-trivial sized or with non-trivial risks would need a testing staff. But whereby the project is for a short term, low risk, small, and with programmers that are highly experienced that are making use of test-first development or unit testing, such project may not need a test engineer for it to do well.

  1. What is verification? And what is validation?

Verifications are reviews and meetings which are intended to help evaluate documents, code, specifications, and requirements. It is usually done with checklists, walkthroughs, issues lists, and inspection meetings.

Validation, on the other hand, entails the real testing and it is done after completing the verification.

  1. What is Regression testing?

This is the act of retesting a program that has been tested previously in order to be sure that there has not been any fault following the modification or that no new fault has been introduced.

  1. What is a ‘test plan’? What is a ‘test case’?

A software project test plan is a document that explains the objective, approach, focus, and scope of a software testing. A test case, on the other hand, is a document that explains an action, input, or event, and a response that is expected, to help decide if an application’s feature is functioning properly.

  1. Why does software have bugs?

Software has bugs for the following reasons

  • Errors in programming
  • Lack of communication or no communications at all
  • Requirements changes
  • Time pressures
  1. What should you do after finding a bug?

You need to report the bug and then assign it to developers that can take care of it. When you have fixed the problem, retest the fixes, decide the requirements for regression testing in order to be sure that no more problems are eventually caused by the fixes.

  1. How can you introduce new Software QA processes to an existing Organization?

This is usually determined by the organization’s size as well as the risks involved. If it is a small project or group, it may be better to use a more ad-hoc process, depending on the customer and project type. It can also be done via incremental self-managed team approaches.

  1. What are 5 common problems in the software development process?
  • Schedule that is unworkable
  • Requirements changes
  • Inadequate communication
  • Insufficient testing
  • Poor requirements
  1. What are the 5 common software development problems solutions?
  • Schedule that is practicable
  • Clear communication among the project team members
  • Firm requirements
  • Clearness of requirements
  • Sufficient testing
  1. What steps are needed in developing and running software test?
  • Get the requirements, functional design, and plan for the internal design, and other documents that are relevant.
  • Get budget and the schedule conditions
  • Decide project framework
  • Recognize risks
  • Decide testing approaches, process, test setting, test data
  • Carry out test
  • Carry out reviews and evaluations
  • Sustain and keep documents up to date
  1. What is the best software test estimation approach?

This is determined by the organization, the type of project, and the experience of the involved personnel. However, here are a few approaches to consider:

  • Metrics-Based Approach
  • Implicit Risk Approach
  • Percentage-of-Development Approach
  • Test Work Breakdown Approach
  • Iterative Approach
  1. How does a client/server environment affect testing?

Client/server applications are sometimes complex as a result of the multiple dependencies among clients, communication of data, server, and hardware, particularly multi-tier systems. Stress/load/performance testing can help to determine the capabilities and limitations of client/server application.

  1. What are the attributes of a good software QA engineer?

They should be able to comprehend the whole process of software development and how it blends with the organization’s goal and the business approach. Diplomacy and patience are highly required in the early phases of QA processes implementation. For inspections and reviews to be successful, ability to identify problems and spot ‘what is missing’ is a must.

  1. What information does a test strategy capture?

It captures the general approach’s explanation to be used as well as the testing styles, specific types, and techniques.

  1. How can we test World Wide Web sites?

Things to consider might include:

  • Testing the HTML specification, internal and external links
  • Testing the server’s expected loads
  • Testing the securities needed to be implemented and verified
  • The applets, ActiveX components, cgi programs, javascript, etc that you need to track, maintain, and control
  • Performance that you should anticipate on the side of the client.


  1. What is extreme programming and what has it got to do with testing?

Extreme programming otherwise known as ‘XP’ is a software development step taken by small teams working on projects that are susceptible to risk and also have requirements that are not steady. To carry out extreme testing, it is expected that the programmers should first write unit and functional test codes before the application code is written. It is also important to make the customer an important part of the project team and assist in developing scenarios that would enable you to conduct acceptance/black box testing.

  1. What is ‘good code’? What is ‘good design’?

‘Good code’ is a code that works well, has no bug, can be read, and can be maintained. Good internal design signifies a software code with a clear, understandable, modifiable, and maintainable overall structure. It has to be robust with the capacity for adequate error handling and status logging and works properly when it is executed. Good functional design refers to an application with a functionality that one can trace back to the requirements of the end-user and customers.


  1. How can you know when to stop testing?

The following factors determine when to stop testing:

  • Deadlines such as testing deadlines, release deadlines, etc are met
  • Test cases are completed with ‘pass’ in certain percentage
  • Exhaustion of test budget
  • Coverage of code/requirements/functionality attains a specified point
  • A drop in the rate of bug below a certain level
  • An end of the beta or alpha testing phase
  1. What if there is not enough time for detailed testing?
  • Decide where to focus the testing with the help of risk analysis
  • Decide which important functionality is to be tested
  • Establish the aspects of the project that are high-risk
  • The kinds of test to be performed have to be prioritized
  • The tests to have the best high-risk-coverage to time-required ratio have to be decided.


  1. What is the main objective when reviewing a software deliverable?

To discover fault in any software work product

  1. What determines the level of risk?

The level of risk is determined by the likelihood of an adverse event and the impact of the event

  1. What is the benefit of test independence?

It prevents the partiality of the author in defining effective tests.

  1. What is SEI? CMM? CMMI? ISO? Will it help?

They are all standards that decide effectiveness in quality software delivery. They help organizations in identifying best practices that are valuable in assisting them in increasing the maturity of their processes.

  1. What is integration testing?

This is the testing carried out to be sure of the accurate operation of the components in the implementation model when combined to execute a use case.

  1. What is developer testing?

Developer testing refers to the aspect of test design and implementation that the team of developers considers most appropriate to undertake.

  1. What is system testing?

It is the series of tests aimed at making sure that the modified program is able to interact properly with other components of the system.

Here is a list of commonly asked basic level Software Testing Interview Questions.You must prepare about different types of testing and about the commonly used Words in Software Testing before attending the Interview.

  1. What are the importance of Software Testing?
  2. What are the main tools you are used for Software Testing?
  3. What are the different types of Software Testing?
  4. What are the difference between Black Box and White Box testing?
  5. What are the difference between Manual Testing and Automated Testing ?
  6. What is Unit Testing ?
  7. What is Integration Testing ?
  8. What is acceptance testing ?
  9. What is Static testing?
  10. What is System testing?
  11. What is Load Testing?
  12. What is Smoke Testing?
  13. What is Soak Testing?
  14. What is Scalability Testing?
  15. What is Sanity Testing?
  16. What is Ramp Testing?
  17. What is Monkey Testing?
  18. What is Gray Box Testing?
  19. What is Functional Testing?
  20. What is Glass Box Testing?
  21. What is Dynamic Testing?
  22. What is Compatibility Testing?
  23. What is Concurrency Testing?
  24. What is Component Testing?
  25. What is Ad Hoc Testing?
  26. What is Agile Testing?
  27. What are the different phases in Software Testing?
  28. How you define defects and Bugs?
  29. What are the roles of a QA specialist?
  30. What is Test Case and Test Plan ?
  31. Tell me about Top Down and Bottom Up approaches in testing?
  32. Tell me about Software Testing Life cycle

Other Testing Related Interview Questions

  1. LoadRunner Interview Questions
  2. WinRunner Interview Questions