MANUAL TESTING

1. What is Software Testing?

Software Testing is the process of verifying and validating a software application to ensure it meets the
specified requirements and is free of defects.

2. What are the different types of Software Testing?

 Functional Testing (e.g., Unit, Integration, System, UAT)

 Non-Functional Testing (e.g., Performance, Security, Usability, Compatibility)

 Maintenance Testing (e.g., Regression, Retesting)

3. What is the difference between Verification and Validation?

Verification Validation

Ensures software meets requirements Ensures software meets user needs

Performed during development Performed after development

Examples: Reviews, Walkthroughs Examples: Testing, UAT

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

STLC Phases:

1. Requirement Analysis

2. Test Planning

3. Test Case Development

4. Test Environment Setup

5. Test Execution

6. Test Closure
5. What is a Test Case?

A Test Case is a document that contains test steps, expected results, and actual results to validate a
functionality.

Example:

Test Case ID Description Steps Expected Result

TC_001 Login Functionality Enter valid credentials & click login User logs in successfully

6. What is the difference between Test Case and Test Scenario?

Test Case Test Scenario

Detailed document with steps High-level description of functionality

Example: Verify login with valid credentials Example: Test login functionality

7. What is the difference between Functional and Non-Functional Testing?

Functional Testing Non-Functional Testing

Tests features & functionalities Tests performance, security, usability

Example: Login validation Example: Load testing

8. What is the difference between Smoke Testing and Sanity Testing?

Smoke Testing Sanity Testing

Basic tests to check if the build is stable Checks specific functionality after changes

Example: App opens & main features work Example: Verify a fixed bug

9. What is Regression Testing?

Regression Testing ensures that new changes do not break existing functionalities.

Example: If a new feature is added, previous features should still work fine.
10. What is the difference between Retesting and Regression Testing?

Retesting Regression Testing

Tests failed test cases again Tests the whole application

Performed only on failed cases Performed on unchanged & changed areas

11. What is Boundary Value Analysis (BVA)?

BVA is a testing technique that checks boundary limits of input values.

Example: If a field accepts values 1-100, test with 0, 1, 100, 101.

12. What is Equivalence Partitioning?

Divides input data into valid and invalid partitions to reduce test cases.

Example: For a field accepting 1-100, valid partitions: 1-100, invalid: <1, >100.

13. What is a Defect Life Cycle (Bug Life Cycle)?

Stages of a defect from detection to closure:

1. New → 2. Assigned → 3. In Progress → 4. Fixed → 5. Retest → 6. Closed

14. What are Severity and Priority in Defects?

Severity Priority

Impact of the bug Urgency to fix the bug

Example: System crash (High Severity) Example: Minor UI issue (Low Priority)

15. What is Exploratory Testing?

Exploratory Testing is an informal test design approach where testers explore the application without
predefined test cases.
16. What is Ad-hoc Testing?

Ad-hoc Testing is an informal testing type without a structured approach.

17. What is Black Box vs White Box Testing?

Black Box Testing White Box Testing

Tests without looking at the code Requires knowledge of the code

Example: UI testing Example: Unit testing

18. What is API Testing?

API Testing ensures that APIs return the correct responses for requests.

Tools: Postman, RestAssured

19. What is Difference Between Static and Dynamic Testing?

Static Testing Dynamic Testing

Done without executing code Done by executing code

Example: Code reviews Example: System testing

20. What is UAT (User Acceptance Testing)?

UAT is the final testing phase where users verify if the application meets their needs before release

1. What is SDLC?

SDLC (Software Development Life Cycle) is a structured approach to software development that defines
phases from planning to deployment and maintenance.

2. What are the phases of SDLC?

1. Requirement Gathering & Analysis – Understanding user needs.

2. Planning – Defining scope, timeline, and budget.

3. Design – Creating system architecture & UI/UX.

4. Implementation (Coding) – Developers write code.

5. Testing – Finding and fixing defects.

6. Deployment – Releasing the software.

7. Maintenance – Bug fixes & improvements.

3. What are the different SDLC models?

1. Waterfall Model – Sequential process, each phase depends on the previous one.

2. V-Model (Verification & Validation Model) – Testing happens in parallel with development.

3. Incremental Model – Software is developed in small parts (increments).

4. Agile Model – Iterative approach with continuous feedback (Scrum, Kanban).

5. Spiral Model – Risk-based model with iterative development.

6. Big Bang Model – No formal planning, suitable for small projects.

4. What is the difference between Waterfall and Agile models?

Feature Waterfall Agile

Approach Sequential Iterative

Flexibility Less flexible More flexible

Customer Involvement Limited Continuous feedback

Testing Phase After development Continuous testing

Best For Large, well-defined projects Dynamic, fast-changing projects

Agile is a flexible SDLC model where software is developed in short iterations (sprints). It emphasizes
customer feedback, collaboration, and continuous improvement.

Example Frameworks:

 Scrum – Uses sprints (2-4 weeks) & daily stand-up meetings.

 Kanban – Uses boards to track progress (e.g., To-Do, In Progress, Done).

6. What is the V-Model in SDLC?

The V-Model (Validation & Verification Model) is an SDLC model where development and testing
happen in parallel. Each development phase has a corresponding test phase.

Example:

 Requirement Analysis ↔ Acceptance Testing

 Design ↔ System Testing

 Implementation ↔ Unit Testing

7. What is the difference between SDLC and STLC?

Feature SDLC (Software Development Life Cycle) STLC (Software Testing Life Cycle)

Purpose Develop software Test software

Planning, Design, Coding, Testing, Test Planning, Test Case Development, Test
Phases
Deployment, Maintenance Execution, Defect Reporting

Outcome Working software Bug-free, quality software

8. What is the purpose of Requirement Analysis in SDLC?

In this phase, business needs are gathered, documented, and analyzed to ensure the software meets
user expectations.

Key Documents:

 SRS (Software Requirement Specification)

9. What is Prototyping in SDLC?

Prototyping is the process of building a rough version of the software to get early feedback before full
development.

10. What is Risk Management in SDLC?

Risk Management identifies, analyzes, and mitigates risks during software development.

Example Risks:

 Technical risks (e.g., outdated technology)

 Business risks (e.g., changing requirements)

 Security risks (e.g., data breaches)

11. What is the difference between Functional and Non-Functional Requirements?

Functional Requirements Non-Functional Requirements

Define what the system should do Define how the system should perform

Example: Login functionality Example: System should handle 1000 users at a time

12. What is Continuous Integration (CI) and Continuous Deployment (CD)?

 CI (Continuous Integration): Automating code integration and testing.

 CD (Continuous Deployment): Automatically deploying software after successful testing.

Tools: Jenkins, GitHub Actions, GitLab CI/CD.

13. What is DevOps and how does it relate to SDLC?

DevOps is a culture that integrates development (Dev) and operations (Ops) to improve collaboration,
automation, and software delivery speed.
Key Practices:

 Continuous Integration (CI)

 Continuous Deployment (CD)

 Infrastructure as Code (IaC)

14. What is the importance of Testing in SDLC?

Testing ensures software quality, reliability, and security by detecting and fixing defects before
deployment.

15. What are Software Maintenance Types in SDLC?

1. Corrective Maintenance – Fixing bugs.

2. Adaptive Maintenance – Updating software for new OS/hardware.

3. Perfective Maintenance – Enhancing performance.

4. Preventive Maintenance – Preventing future issues