Smoke Test Deck

Question 1

What is a Good Smoke Test ?

Answer 1

The goal of a smoke test is to see if developers achieved a degree of stability.

test of major functionality and shows product is ready for further test like functional testing

This saves time, faster bug resolution, enables quality improvement

Question 2

What are the critical scenarios that need to be included in a smoke test?

Answer 2

Build Verification

Account Creation - try to create new user , new creds

Login/Logout

Business Critical Features - most commonly used funcs

Integration scenarios - make sure system doesn’t break in any integration points

Add/Edit/Delete - do an entry for these 3 to ensure proper database connectivity

Overall Navigation - touch frequently used funcs and pages

Question 3

What would you do to limit smoke tests?

Answer 3

I would focus on the critical scenarios but if that is too much of a starting point, I would reach out to Product Owner and ask what they would want most

Question 4

Can you give an example of a Smoke Test?

Answer 4

DESCRIPTION
To check video launch functionality

STEPS

1. Go to the video page
2. Click the video

EXPECTED RESULT = Smooth playback of the video

ACTUAL RESULT = Video player not popping up

STATUS - fail

Question 5

What are 5 types of Severity ?

Answer 5

Critical, Major, Moderate, Minor, Cosmetic

1. Critical – User clicks forget password, enters OTP(correct or incorrect) and a loader continues to spin indefinitely , user can login to access functionalities
2. Major- User can log in without validating password which is unauthorized access
3. Minor – User logs in with correct username and password but is shown “Login unsuccessful, please try again later” , still has access to functionalities
4. Cosmetic – password field is placed above username field or spelling error

Question 6

What are the levels of Priority ?

Answer 6

Immediate - Misspellings that could lead to losses in business

High - E-Commerce site crashes when item added to cart

Medium - Make a purchase, item shows as added but it says Payment Unsuccessful

Low - navigation bar is misaligned or misspelling in body

Question 7

What are examples of the following :

High Severity, High Priority

Low Severity, High Priority

High Severity, Low Priority

Answer 7

HS, HP = Login button not clickable

LS, HP = company name has misspelling

HS, LP = app is not loaded properly or completely on old version of Internet Explorer but there is so few users

Question 8

How would you decide what to prioritize in terms of testing to make mini regression test suite?

Answer 8

1. Select test cases with frequent defects // look at past releases & sprints
2. importance of the usability of the feature in app
3. chooses tests with critical funcs like login, edit, add
4. frequent code changes
5. end to end test flows - the entire process for adding new payment for a mobile bank app
6. field validation test cases - inputting details in a mandatory field , does it show error message or continues

Question 9

What is the difference between Smoke and Sanity testing ?

Answer 9

Sanity is for minor areas and funcs

It is a subset of regression testing

It is done by software testers

if the build has 3 modules: Login, Admin, Employee, they test the main funcs without going deeper, thats sanity.

Question 10

What are components that are necessary for a Test Plan ?

Answer 10

Introduction - includes the purpose and scope of the project

Features to Be Tested:
features to be tested are Login Page, Dashboard, Reports

Deliverables - list of docs need to be delivered at each phase of testing life cycle
EX: test cases, bug report

Pass/Fail Criteria:
Ex: all major func of the app should work as intended and the pass percentage of test cases should be more than 95% and there should not be any critical bugs