Agile methodology
Table of contents
No headings in the article.
- Smoke and Sanity Testing
Smoke testing
Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine
The objective of this testing is to verify the “stability” of the system in order to proceed with more rigorous testing
This testing is performed by the developers or testers
Smoke testing is usually documented or scripted
Smoke testing is a subset of Acceptance testing
Smoke testing exercises the entire system from end to end
Sanity Testing
Sanity Testing is done to check the new functionality/bugs have been fixed
The objective of the testing is to verify the “rationality” of the system in order to proceed with more rigorous testing
Sanity testing in software testing is usually performed by testers
Sanity testing is usually not documented and is unscripted
Sanity testing is a subset of Regression Testing
Sanity testing exercises only the particular component of the entire system
Validation and Verification
Validation
We check whether the developed product is right.
Validation is also known as dynamic testing.
Validation includes testing like functional testing, system testing, integration, and User acceptance testing.
It is a process of checking the software during or at the end of the development cycle to decide whether the software follow the specified business requirements.
Quality control comes under validation testing.
In validation testing, the execution of code happens.
In the validation testing, we can find those bugs, which are not caught in the verification process.
Validation testing is executed by the testing team to test the application.
After verification testing, validation testing takes place.
In this type of testing, we can validate that the user accepts the product or not.
Verification
We check whether we are developing the right product or not.
Verification is also known as static testing.
Verification includes different methods like Inspections, Reviews, and Walkthroughs.
It is a process of checking the work-products (not the final product) of a development cycle to decide whether the product meets the specified requirements.
Quality assurance comes under verification testing.
The execution of code does not happen in the verification testing.
In verification testing, we can find the bugs early in the development phase of the product.
Verification testing is executed by the Quality assurance team to make sure that the product is developed according to customers' requirements.
Verification is done before the validation testing.
In this type of testing, we can verify that the inputs follow the outputs or not.
- Explain about agile methodology?
Agile software development is a process for developing software like waterfall model,v-model etc.However,agile methodology differs significantly from other methodologies. In English, Agile means'ability to move quickly and easily' and responding swiftly to change, this is a key aspect of agile software development as well.
Example: Adobe is working on project to come up with a competing product for Microsoft Word, that provides all the features provided by Microsoft Word and any other features requested by the marketing team. The final product needs to be ready in 10 months of time. Let us see how this project is executed in traditional and Agile methodologies.
- Explain about epic and user stories?
Epic
An epic is a large chunk of work that is segmented into smaller tasks, called user stories. An epic often spans across multiple sprints, teams, and even across multiple projects. Product people need to break down epics into stories before they can start creating functionality from them.
User stories
User stories are a key component of agile software development. They are short, simple descriptions of a feature or functionality from the perspective of a user. User stories are used to capture requirements in an agile project and help the development team understand the needs and expectations of the users.