Difference between Sanity and Smoke testing:

SANITY:

• Sanity Testing is done by testers.
• Sanity Testing verifies the new functionality like bug fixes.
• Sanity testing is a subset of Regression Testing.
• Sanity Testing verifies only a particular component.

SMOKE:

• Smoke Testing is done by both developers and testers.
• Smoke Testing verifies the critical functionalities of the system.
• Smoke testing is a subset of acceptance testing.
• Smoke testing verifies the entire system from end to end.

Difference between validation and verification:

VALIDATION:

• Purpose:
  Validation focuses on ensuring that the software meets the requirements and expectations of the customer.

• Process:
  It involves testing and validating the actual product.

• Testing Type:
  Validation is a dynamic testing process.

• Execution of Code:
  It includes the execution of the code.

• Methods Used:
  Black Box Testing, White Box Testing, and non-functional testing are used for validation.

• Goal:
  The goal of validation is to validate the actual product.

• Timing:
  Validation begins as soon as the project starts.

• Defect Detection:
  It can find bugs that could not be found during the verification process.

• Responsibility:
  Validation is executed by the testing team.

VERIFICATION:

• Purpose:
  Verification focuses on ensuring that the software correctly implements the specific function or feature.

• Process:
  It involves checking documents, design, codes, and programs.

• Testing Type:
  Verification is a static testing process.

• Execution of Code:
  It does not include the execution of the code.

• Methods Used:
  Reviews, walkthroughs, inspections, and desk-checking are commonly used methods for verification.

• Goal:
  The goal of verification is to validate the application and software architecture against specifications.

• Timing:
  Verification occurs before validation.

• Defect Detection:
  It can find bugs in the early stages of development.

• Responsibility:
  The quality assurance team typically handles verification.

AGILE METHODOLOGY:

Agile is a people-focused, results-driven approach that respects our rapidly changing world. It centers around adaptive planning, self-organization, and short delivery times, using frameworks like Scrum and extreme Programming. Whether in software development or other domains, Agile has proven successful for teams aiming to deliver value efficiently and collaboratively.

EPIC AND USER STORIES:

• Stories:
  also called “user stories,” are short requirements or requests written from the perspective of an end user.

• Epics:
  are large bodies of work that can be broken down into a number of smaller tasks (called stories).