Agile Methodology
Tags: agile, testing, sdlc, stlc
Published: 2023-08-25 10:54:34

## Smoke Testing :-

> - Smoke Testing is one of the Functional testing to helps the Software build & It is also called as _Build Verification Testing_ (OR) _Build Acceptance Testing_. 
> - In software Testing process The Smoke Tests is to verifying the important features are working correctly or not and to identify the Bugs in the testing.
> - Smoke Testing is the Important testing in Initial stage whether any issues in that function or the bug has found in this Initial stage Test effort, Time Consuming, Cost effects are easily can be overcome.

## Sanity Testing :-

> - Sanity Testing is one of the Functional testing to test the Minor change or New Build has released from the Developer team.
> - Sanity testing is to evaluate that all the defects have been solved and no added issues come after the new build has been released.
> - In this Testing is to verify the Whether the New Build doesn't affect the old working functionalities. Sanity Testing is a _Mini Regression Testing_.

## Difference Between Smoke & Sanity Testing :-

- _Smoke Testing_ is to Check the Critical Functionalities of the program is working fine & _Sanity Testing_ is to check the New functionality (or) Bugs have been fixed.

- _Smoke Testing_ is done in Initial Stage of the Testing process & The _Sanity Testing_ is Done when New Bugs has been found or New Build has been released.

- _Smoke Testing_ is also called as Build Verification Testing(BVT) or Build Acceptance Testing(BAT) & _Sanity Testing_ is also called as Mini Regression Testing.

- _Smoke Testing_ is to Test the Major and Minor functionality of the Software module & _Sanity Testing_ is to test the Specific Software module.

- _Smoke Testing_ is done by either Developer or Tester & _Sanity Testing_ is done only by the Tester.

- _Smoke Testing_ is check all software modules & _Sanity Testing_ only check the _Sanity Testing_ is check only the defect or modify modules.


## Validation :-

> - Validation is like if the software product actually meets the exact needs of the customer or not. The Validation process is to check the software that fulfills the Customer needs and azure the working condition of Software in High quality.

## Verification :-

> - Verification is like a process of Checking Documents, Design, Code to check if the software has been built according to the requirements or not. The aim of verification process is to check the quality of Software Application were designed.

## Difference Between Validation & Verification :-

- _Validation_ checks only the Developed Product is right & 
_Verification_ checks the Developing product is right.

- _Validation_ involve in Basic Functional testing & _Verification_ involve in checking Inspection, Reviews and Documents.

- _Validation_ check the software at the end of the development cycle & _Verification_ check the software In between the development stage process.

- _Validation_ comes after the Verification process & _Verification_ comes First and after only Validation process comes in.

- _Validation_ work with Code in Functional Testing & _Verification_ work with Detailed Documents.

## Agile Model

> - Agile model is a one of the most widely used SDLC Process for developing the software application in all Industry.

> - Nowadays it is widely use in process and it is easy to approach with collaborative to team members, with Clients, Project Stage, Results, Feedbacks from Customers feedback etc...,
Scrum
> - SCRUM is an agile project management process used to build software development based on Weekly Sprint meeting, Review Meeting and Retrospective meeting.

- Scrum Master: The Scrum Master lead the Scrum team for developing the software. Scrum Master arrange the meeting, Helps the Product owner and Support organization.

- Product owner: The Product owner Knows the Aim of the Product and he is the In-charge of the product development and
He communicate with Development Team and Master.

- Scrum Team: In Scrum Team each member is responsible for
delivering High quality product with collaboration with each other and self motivated.

## Epic and User Story:-

**Epic**:
> - A Epic can be defined as a _Task_ (or) _User Story_ that can be divided into several smaller User Stories like _Sub-task_ as per the customer's requirements.
> - The requirement of the software product is a divided into the collection of Epics and each Epics contains Tasks and Sub-tasks.
> - It helps the Agile team to know about the Roadmap of Product and Product workflow condition and Decision-making easily.

**User Story**:
> - A User story is the smallest unit of work in an agile framework and the User story is usually written from the user's perspective way.
> - The aim of a user story is little a piece of work are divided and it will deliver a valuable product back to the customer.
> - The user story describes the user requirement, what they want and why? and they are very easy to understand.