Skip to main content

Part 1-Interview questions for Manual testing

1. What is Software Testing?

Answer: Software testing is the process of evaluating a software application to identify any discrepancies between expected and actual outcomes, ensuring the product is defect-free and meets user requirements.​GUVI

2. What are the different types of Software Testing?

Answer: The main types include:​Software Testing Material+1LinkedIn+1

  • Functional Testing: Validates the software against functional requirements.​

  • Non-Functional Testing: Assesses aspects like performance, usability, and reliability.​

  • Manual Testing: Test cases are executed manually without automation tools.​Software Testing Material+2LinkedIn+2Katalon Test Automation+2

  • Automation Testing: Utilizes scripts and tools to perform tests automatically.​

3. What is the difference between Verification and Validation?

Answer:

  • Verification: Ensures the product is designed correctly, focusing on processes and methodologies.​

  • Validation: Ensures the built product meets user needs and requirements, focusing on the actual product.​

4. What is a Test Case?

Answer: A test case is a set of conditions and steps used to determine whether a software application functions as intended.​ArtOfTesting+2GUVI+2LinkedIn+2

5. What is a Test Plan?

Answer: A test plan is a document outlining the scope, approach, resources, and schedule of intended testing activities.​

6. What is the Software Development Life Cycle (SDLC)?

Answer: SDLC is a process used by the software industry to design, develop, and test high-quality software.​

7. What is the Software Testing Life Cycle (STLC)?

Answer: STLC refers to the sequence of activities conducted to perform software testing, including phases like requirement analysis, test planning, test case development, environment setup, test execution, and test closure.​LinkedIn

8. What is Black Box Testing?

Answer: Black box testing assesses the functionality of an application without peering into its internal structures or workings.​

9. What is White Box Testing?

Answer: White box testing involves testing internal structures or workings of an application, ensuring that all internal operations perform as expected.​

10. What is Grey Box Testing?

Answer: Grey box testing is a combination of black box and white box testing methodologies, where the tester has partial knowledge of the internal workings of the application.​

11. What is Unit Testing?

Answer: Unit testing involves testing individual components or pieces of code to ensure they function correctly.​

12. What is Integration Testing?

Answer: Integration testing verifies that different modules or services used by your application interact correctly.​Software Testing Material

13. What is System Testing?

Answer: System testing evaluates the complete and integrated software to assess the system's compliance with the specified requirements.​ArtOfTesting+1LinkedIn+1

14. What is Acceptance Testing?

Answer: Acceptance testing determines whether the software system has met the required specifications and is ready for delivery to the end-user.​

15. What is Regression Testing?

Answer: Regression testing involves re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change.​

16. What is Smoke Testing?

Answer: Smoke testing is a preliminary test to check the basic functionality of the application.​

17. What is Sanity Testing?

Answer: Sanity testing is a subset of regression testing, focusing on verifying specific functionalities after making minor changes to the code.​

18. What is Exploratory Testing?

Answer: Exploratory testing involves testers exploring the application without predefined test cases, relying on their intuition and experience.​

19. What is Ad-hoc Testing?

Answer: Ad-hoc testing is an informal testing phase where the tester tries to break the system by randomly trying the system's functionality.​

20. What is Usability Testing?

Answer: Usability testing evaluates a product by testing it on users to measure how user-friendly, efficient, and satisfactory the product is.​

21. What is Compatibility Testing?

Answer: Compatibility testing checks whether your software can run on different hardware, operating systems, applications, network environments, or mobile devices.​

22. What is Performance Testing?

Answer: Performance testing determines the speed, responsiveness, and stability of a system under a workload.​

23. What is Load Testing?

Answer: Load testing assesses the system's performance under expected user loads to identify performance bottlenecks.​

24. What is Stress Testing?

Answer: Stress testing evaluates how the system operates under extreme conditions, such as high traffic or data processing.​

25. What is Volume Testing?

Answer: Volume testing checks the system's performance by loading it with a large volume of data.​

26. What is Security Testing?

Answer: Security testing identifies vulnerabilities, threats, and risks in a software application to prevent malicious attacks.​

27. What is Alpha Testing?

Answer: Alpha testing is conducted in the development environment by internal staff before releasing the product to external users.​

28. What is Beta Testing?

Answer: Beta testing is performed by real users in a real environment to validate the product's functionality, usability, and compatibility.​

29. What is the difference between Test Strategy and Test Plan?

Answer:

  • Test Strategy: A high-level document outlining the testing approach, objectives, and resources.​

  • Test Plan: A detailed document describing the scope, approach, resources, and schedule of testing activities.

 

Comments

Post a Comment

Popular posts from this blog

Understanding XML for QA Testing

 As a QA tester, working with XML is essential, especially for API testing, data validation, and automation . Today, I explored the key concepts every QA should know about XML. 🔹 What is XML? XML ( eXtensible Markup Language ) is used for storing and transporting data in a structured format. It’s widely used in APIs (SOAP), test data, and configurations . 🔹 Why QA Testers Should Learn XML? ✅ API Testing – SOAP APIs use XML for requests & responses. ✅ Test Data Handling – XML is used in test scripts, Selenium, and data-driven testing. ✅ Config Files – Many automation tools (TestNG, Jenkins) use XML for setup. 🔹 Key XML Concepts for QA 📌 XML Structure – Elements, attributes, nesting, and schema validation. 📌 XPath – Used for locating XML nodes in automation & API testing. 📌 XML Schema (XSD) – Ensures data correctness in APIs. 📌 Parsing XML – Reading & extracting values using tools like Postman, Python, or Java . 💡 Where to Learn XML? 📖 W3Scho...
Post a Comment
Read more

30 Manual Testing interview questions from glass door

Here are 30 manual testing interview questions commonly encountered in interviews, compiled from various sources including Glassdoor: What is the difference between Quality Assurance (QA), Quality Control (QC), and Software Testing? QA focuses on improving the processes to deliver Quality Products. QC involves the activities that ensure the verification of a developed product. Software Testing is the process of evaluating a system to identify any gaps, errors, or missing requirements. Can you explain the Software Testing Life Cycle (STLC)? The STLC includes phases such as Requirement Analysis, Test Planning, Test Case Development, Environment Setup, Test Execution, and Test Closure. What is the difference between Smoke Testing and Sanity Testing? Smoke Testing is a preliminary test to check the basic functionality of the application. Sanity Testing is a subset of regression testing to verify that a specific section of the application is still worki...
Post a Comment
Read more

QA Automation journey

🔥 50-Day QA Automation Learning Plan (TS + Playwright) Day Topic Focus 🔹 Phase 1: Foundations (Days 1–10) | 1 | Introduction to Test Automation & Testing Pyramid | What, why, and how of automation | | 2 | Intro to JavaScript & TypeScript | Setup, syntax overview | | 3 | Variables, Data Types, Constants | Hands-on coding | | 4 | Functions, Loops, Conditionals | Practice basic logic | | 5 | Classes & Constructors in TS | OOP basics | | 6 | Setup Playwright Project | Install, basic structure | | 7 | First Test with Playwright | Run test, understand selectors | | 8 | Debugging in Playwright | Logs, retries, timeout handling | | 9 | Folder Structure & Best Practices | Test organization | | 10 | Recap & Mini Project | Small Playwright test project | 🔹 Phase 2: Unit & API Testing (Days 11–25) | 11 | What is Unit Testing? | Concept + console app example | | 12 | Annotations & Test Hooks | beforeAll, afterEach, etc. | | 13 | Parametrized...
Post a Comment
Read more