Agile Methodology

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.