Skip to main content

Smoke Testing vs Sanity Testing


Differences between Smoke Testing and Sanity Testing are as follows:

Topic
Smoke Testing
Sanity Testing
Purpose
To verify the BASIC or CRITICAL existing functionality of an Application- before starting rigorous testing.
To verify NEWLY ADDED/UPDATED functionality or BUG FIXES.
Who does these testing?
Performed by both TESTERS and DEVELOPERS
Performed only by TESTERS
Can these tests be automated?
Can be automated
Can’t be automated
In technical terms
Exercises the ENTIRE system from END-TO-END
Exercises only a particular COMPONENT of the entire system
In general terms
SHALLOW and WIDE range of testing.
More like a GENERAL HEALTH CHECKUP
Narrow and DEEP approach of testing.
More like a SPECIALIZED HEALTH CHECKUP








Comments

Popular posts from this blog

Effective Scrum Meeting

Overview: The Daily Scrum Meeting is held every day through the sprint. At the meeting, the Scrum team gathers to review and synchronize about the project status. In theory, each team member should provide his/her status based on three (03) Q: What did you do yesterday? What do you intend to do today? Is there any issues that blocks your work? # The participants should come prepared: Stop participants that don't come prepared and waste the meeting time. The team members should come prepared to share their updates. You should describe how to answer these questions effectively to increase the synchronization among the team members. The team members should know what is your expectations from them while answering these questions. # Validate that each individual describe the full picture: Validate that each individual can answer the 3 questions (Do not continue until you get the answers or the reasons for why he can't provide them). Validate that each tea...

GitHub- how it works

GitHub: GitHub is a platform for hosting and collaborating on projects. We don’t have to worry about losing data on our hard drive or managing a project across multiple computers — sync from anywhere. GitHub Essentials:   Repositories ,   Branches , Commits ,   Issues   and   Pull Requests . A   repository   is the basic unit of GitHub, most commonly a single project.  Repositories can contain folders and files, including images – anything our project needs. Repository = single project = single folder which contains subfolders and files. Sometimes GitHub users shorten this to “repo.” Branching   is the way to work on different parts of a repository at one time. When we are working on a project, we are going to have a bunch of different features or ideas in progress at any given time – some of which are ready to go, and others which are not. Branching exists to help we manage this workflow. When we create ...

Verification and Validation (V&V)- a software testing approach

Verification: It focuses on PROCESS related activities to ensure that the Products and deliverables meet a specific requirement before the final testing. Can be done through: A. Technical review B. Business review C. Management review Simply: Are we building the product in the right way?  that is, does the software conform to its specification verification  is the process of checking that the software meets the specification. Verification is an example of QA Validation: It focuses on PRODUCT related activities, that attempt to determine if the system or project deliverables meet the customer or client's expectations. Will be done by: Testing. Simply: Did we build the right product?  that is, is the software doing what the user really requires. Validation  is the process of checking whether the specification captures the customer's needs. According to the Capability Maturity Model(CMMI-SW v1.1) we can also define validation as The process ...