Difference between Smoke Testing and Sanity Testing?
Smoke Testing: Smoke Testing build Verification testing to check the basic functionalities of an application are working after a new build.
If build is stable enough then will continue with further testing. If it fails, the build is rejected for further testing.
-> It verifies an application login, the user interface is visible, and basic navigation works.
It typically happens before regression and targets on basic functionalities of the application.
Sanity Testing: Sanity Testing more focused on specific functionalities or fixes are working after changes.
It typically happens after smoke testing or regression and targets a specific area of the application.
Difference between Regression and Retesting?
Regression Testing: Regression performs to check existing functionality is not impacted due to the changes. These changes can be on
-> new build release
-> bug fixes
-> environment changes
Re-Testing: Retesting focuses on bug fix to make sure that previously identified defect has been fixed.
Deference between integration testing and System testing?
Integration Testing: It conducts on different modules or components of the system work together as expected.
It focuses on the interfaces and communication between modules.
System Testing: It checks entire system as a whole against both functional and non-functional aspects.
It involves testing the system’s overall functionality, performance, security, and compatibility.
We check all integrated modules, interfaces and external dependencies works as unified system and meets business requirements.
-> System testing comes after integration testing and before acceptance testing.
What is UAT (User Acceptance Testing)?
User Acceptance Testing is final phase of software testing where software being tested by the end users to ensure that it meets their needs and requirements.
It is typically performed after all testing activities (such as unit, integration, regression and system testing) are completed and the software is ready for deployment.
Here, users test the software, execute test scenarios with real data, and document their findings (like issues, feedback, and improvements).
User Acceptance Testing (UAT) can be performed in two ways:
Alpha Testing: Alpha testing will be conducted inside the development organization in the presence of end users or customer.
Beta Testing: Beta testing will be conducted Outside the development organization in the presence of end users or customer.
