Q1)DIFFERENCES BETWEEN
VERIFICATION
1)Focuses on whether the software meets its specified requirements
2)Typically conducted during the development process
3)Involves testing at the component, module, and system levels
4)Involves testing with sample data
5)Designed to catch defects early in the development process
6)Examples include unit testing, integration testing, and system testing
7)Helps to ensure that the software is built correctly
8)Helps to increase confidence in the software
9)Improves the quality of the software
10)Can be automated or manual
11)Requires a good understanding of the software requirements and specifications
VALIDATION
1)Focuses on whether the software meets the needs of end-users
2)Typically conducted after the development process
3)Involves testing the software as a whole
4)Involves testing with real-world data
5)Designed to catch defects before release to end-users
6)Examples include user acceptance testing, alpha and beta testing, and compatibility testing
7)Helps to ensure that the correct software is built
8)Helps to increase user satisfaction
9)Reduces the risk of product recalls or legal issues
10)Often involves manual testing
11)Requires a good understanding of end-user needs and expectations
Example:
1)Verification of SUBMIT BUTTON in any Form or application
In verification aspect first we need to verify whether the submit button is available or not which in correct format correct place in correct manner or not.
Where as in validation process the application should have to perform some action whenever the user hits on the submit button.
Which would either save the data to the database or displays error message for the invalid data.
Verification starts even before we start the coding and continues throughout the development phase
Validation requires execution of the application after deployment.
SMOKE VS SANITY TESTING
SMOKE TESTING
1)Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine
2)The objective of this testing is to verify the “stability” of the system in order to proceed with more rigorous testing
3)This testing is performed by the developers or testers
4)Smoke testing is usually documented or scripted
5)Smoke testing is a subset of Acceptance testing
6)Smoke testing exercises the entire system from end to end
7)Smoke testing is like General Health Check Up
Example:
1)verifying the user registration and login process
2)Checking the product catalog and shopping cart working as expected
3)verifying the products to add cart proceeded to checkout
4)Checking the payment service to complete the product purchase
5)Veryfing the product order confirmation and tracking order history
SANITY TESTING
1)Sanity Testing is done to check the new functionality/bugs have been fixed
2)The objective of the testing is to verify the “rationality” of the system in order to proceed with more rigorous testing
3)Sanity testing in software testing is usually performed by testers
4)Sanity testing is usually not documented and is unscripted
5)Sanity testing is a subset of Regression Testing
6)Sanity testing exercises only the particular component of the entire system
7)Sanity Testing is like specialized health check up
Example:
1)I want to add products to my shopping basket on an e-commerce website to make a purchase.
Scenario 1: Adding one item to the shopping cart.
Scenario 2: Adding numerous items to the shopping cart.
In Test Case 1, Confirm that a single item may be added to the shopping basket.
Verify that a user may add numerous products to the shopping basket in Test Case 2.
Q2)Explain about Agile methodology?
Automated Testing is a technique where the Tester writes scripts on their own and uses suitable Software or Automation Tool to test the software. It is an Automation Process of a Manual Process. It allows for executing repetitive tasks without the intervention of a Manual Tester.
It is used to automate the testing tasks that are difficult to perform manually.
Automation tests can be run at any time of the day as they use scripted sequences to examine the software.
Automation tests can also enter test data compare the expected result with the actual result and generate detailed test reports.
The goal of automation tests is to reduce the number of test cases to be executed manually but not to eliminate manual testing.
It is possible to record the test suit and replay it when required.
The different types of automation testing:
Unit testing: Unit testing is a phase in software testing to test the smallest piece of code known as a unit that can be logically isolated from the code. It is carried out during the development of the application.
Integration testing: component: Integration testing is a phase in software testing in which individual software components are combined and tested as a group. It is carried out to check the compatibility of the component with the specified functional requirements.
Smoke testing: Smoke testing is a type of software testing that determines whether the built software is stable or not. It is the preliminary check of the software before its release in the market.
Performance testing: Performance testing is a type of software testing that is carried out to determine how the system performs in terms of stability and responsiveness under a particular load.
Regression testing: Regression testing is a type of software testing that confirms that previously developed software still works fine after the change and that the change has not adversely affected existing features.
Security testing: Security testing is a type of software testing that uncovers the risks, and vulnerabilities in the security mechanism of the software application. It helps an organization to identify the loopholes in the security mechanism and take corrective measures to rectify the security gaps.
Acceptance testing: Acceptance testing is the last phase of software testing that is performed after the system testing. It helps to determine to what degree the application meets end users’ approval.
API testing: API testing is a type of software testing that validates the Application Programming Interface(API) and checks the functionality, security, and reliability of the programming interface.
UI Testing: UI testing is a type of software testing that helps testers ensure that all the fields, buttons, and other items on the screen function as desired.
Q3)Explain about EPIC and USERSTORIES?
EPIC ,the word meaning is greater in size.In Agile methodology epic represents a series of userstories that shares broader strategic objective.Epics are a helpful way to organize work and to create a hierarchy.The idea is to break the work into smaller pieces and the project gets done and regularly can update with the enduser or the client.An epic is a large body of work that can be broken down into a number of smaller stories or sometimes called “Issues” in Jira.
An epic is simply a collection of User stories,Which are interrelated to form a large application programme.
Benifits of epic are,Better time management and better organization and also clear cut priorities and customer statis faction.It brings transparency throughout the process.
USERSTORIES are lightweight tasks which covers the epic.During a sprint or iteration planning meeting, the team decides what stories they’ll tackle that sprint. Teams now discuss the requirements and functionality that each user story requires. This is an opportunity to get technical and creative in the team’s implementation of the story. Once agreed upon, these requirements are added to the story.Another common step in this meeting is to score the stories based on their complexity or time to completion. Teams use t-shirt sizes, the Fibonacci sequence, or planning poker to make proper estimations. A story should be sized to complete in one sprint, so as the team specs each story, they make sure to break up stories that will go over that completion horizon.
EXAMPLE:EPIC:Mobile app for an online beauty spa.
User story:1)Augumented reality so that the user a view virtually by applying beauty products.
2)Discounts and proomocodes
3)chat boat functionality for smaller queries.
Top comments (0)