Difference between regression, smoke, and sanity tests

 Reference: https://medium.com/@Jia_Le_Yeoh/difference-between-regression-sanity-and-smoke-testing-ed2129bf049 


Regression Testing:

Regression testing is a procedure that checks whether an application performs as intended after any improvements, updates, or code changes. It is a superset of smoke and sanity testing. It is in charge of the general stability of the build’s existing features. When a change is made, a regression test is run to see if it will hold up over time as the system improves.

After executing sanity tests on any modified functionality, regression testing is performed, leading to Quality Assurance and related functionalities. Only the QA team is in charge of this. Regression testing is the last step in the testing process, and it examines the overall behavior of the product. If you’re doing regression testing, make sure the code you’re testing is in a configuration management tool and that it can be modified while the test is running.

Sanity Testing:

Sanity testing determines whether new module additions to the usual software created. The existing software are stable sufficient in order to move on the next phase of testing. This is also known as Surface Level Testing, and it is required to quickly assess the quality of software regressions. Sanity tests clarify if end-to-end testing of the build can be carried out effortlessly in the case of minor code changes.

Sanity tests also ensure that any changes made do not affect the software build’s other functionality. Sanity testing is a type of regression testing used in quality assurance. It’s a stage after the smoke test has been completed.

Reference: https://medium.com/@Jia_Le_Yeoh/difference-between-regression-sanity-and-smoke-testing-ed2129bf049

Smoke Testing:

Early in the software development life cycle, smoke testing is performed (SDLC). It guarantees that the program’s key functions work together smoothly. Prior to doing functional tests and smoke testing is performed.

Smoke testing is known as the build verification test, search for problems in specific portions of the software rather than the entire application. Because of its simplicity and reduced time commitment, it is used by both testers and developers. It’s a part of the thorough testing process, and it employs test cases to ensure that all critical aspects of the build are in working order.


Reference: https://medium.com/@Jia_Le_Yeoh/difference-between-regression-sanity-and-smoke-testing-ed2129bf049

 

Comments

Post a Comment

Popular posts from this blog

What happens in requirement analysis phase in SDLC?

Image
For any  software development life cycle  (SDLC), the requirement phase is the first step toward unambiguity. It is an essential step because it reverberates with acceptance tests which are crucial for the end user acceptance. Here is the complete process of the requirement analysis and gathering phase of SDLC – Requirement gathering Also known as elicitation, software development requirements gathering is followed by an analysis of the needs so that the technology experts shall go for feasibility tests and may alter some objectives to convert the thoughts into a real product. The gathering technique involves precise research on what customers need. Nevertheless, it is not possible to put a survey questionnaire to each customer and get feedback; hence, the requirement for product, tool, or objectives is asked to the stakeholders who influence the product or who are well acquainted with the end users. The stakeholders could be software quality engineers or at times even...
Read more

What are the drawbacks in waterfall software development mode?

  What is the Waterfall Method? The Waterfall Model is a linear or sequential approach to project management and works based on fixed dates, requirements, and outcomes. Teams do not require consistent communication and, unless specific integrations are required, can be self-contained. Team members can also work independently and are often required to provide status reports somewhat less frequently (when compared to an agile approach). A typical Waterfall project is chronological and is made up of the following phases: Requirements Design Implementation Verification Maintenance Disadvantages of the Waterfall Model 1 . The waterfall model doesn’t support making changes. 2. It can invalidate the work you’ve previously accomplished. 3. This method excludes end-users and clients. 4. It delays testing until after the completion of the project. 5. The waterfall model can promote longer delivery times. 6. It typically works better for small projects. 7. Working m...
Read more