Scribd
Upload
48 views4 pages

SIT Environment: Sanity Testing

This document describes the sanity testing process in a software development environment. It explains that sanity testing is performed when a new build is received from developers to check the build stability and core functionality. If any blocker defects are found, the build is rejected and developers are notified to fix issues. Once issues are resolved, a new build is tested again until it is stable enough for further testing. The document provides details on the different types of tests performed in sanity testing like GUI validation, link validation, and basic functionality validation.

Uploaded by

Akshay Khot
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
48 views4 pages

SIT Environment: Sanity Testing

This document describes the sanity testing process in a software development environment. It explains that sanity testing is performed when a new build is received from developers to check the build stability and core functionality. If any blocker defects are found, the build is rejected and developers are notified to fix issues. Once issues are resolved, a new build is tested again until it is stable enough for further testing. The document provides details on the different types of tests performed in sanity testing like GUI validation, link validation, and basic functionality validation.

Uploaded by

Akshay Khot
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SIT Environment

 What is XYZ testing? Why we are doing these testing? Are we/you preparing any
documents? (TCD, Defect, TCE, etc.), after these testing any documentation send /email
send /inform to Test Lead, PM & BA, etc.?
 When developer will sent the build Inform to Tester throw Mail (JIRA) & attached in
mail Unit Testing document (Step for testing feature+ Tables name)
 Sent the build/ Deployment process (Code  Push to GIT master Brach  Jenkins job
 Dev to SIT environment)
 In SIT environment, Tester is working
 Tester will do TCD, Review (peer review), TCE, defect raised/inform to developer, demo
etc.
 SIT environment different types of testing
1. Sanity testing/Smoke testing
2. System & functionality testing
3. Re-testing & regression testing, etc.
 SIT Environments- URL - https://qa.Paytm.com

Sanity Testing

 Sanity testing- it is first testing in SIT environment


 In sanity testing, tester are involved
 When tester will performed first types of testing in SIT environment, these testing are
called level zero testing / zero level testing
 Sanity testing also called Tester acceptance testing/ Build verification testing
 When tester/we will got New build from developer then tester will check the build
stability i.e. either build is stable for testing these type of testing is called sanity testing
 Main agenda is to check basic & core functionality of the application/ main flow of
application/ happy flow of application & application working flow
 In Sanity testing we will performed or Stability of application in sanity testing
check/validate
1. Validating the Core functionality of application/ feature- ex. Paytm-Recharge-
Recharge for every mobile or Basic & core functionality validation
2. Validating the GUI/ UI of application/ feature or GUI validation
3. Validating link present in application/ feature or Link Validation
4. Validating the tab/pages present in application/ feature or Tab Validation
5. Validating the Navigation or Page validation
1. Basic & Core Functionality validation
 We check main flow of application from start to end or page to page i.e. we check happy
flow
 We check for blocker/show stopper, if we found, we raise that defect/we lock that defect
& assign to the developer
 If we found defects, so according to the small, large, critical we note down those defect
 If we found blocker, we reproduce it 2-3 time before the raising the defect
 Ex. Paytm-Recharge-Recharge for every mobile- in this test, tester validate user can
proceed for next stage
 Recharge Module-


 Recharge Mobile/ Amount/ Promo Payment – debit
Thank
2.
Icon Tab Validation
circle tab Plan info code card, etc
message
 We check functionality of tab, where we enter characters, special characters, numbers,

3. Tab Validation
 We check functionality of tab, where we enter characters, special characters, numbers,
symbols & we check whether this text box is accepting it or not
 Whenever we enter any value in tab by using on screen keyboard or physical keyboard,
those characters, special characters, numbers, symbols should get entered in tab

4. Link Validation
 In this validation, sequence of interlink pages are tested
 Ex. if I click on flight, then flight information page should open, so, developer should
provide link of that page to the icon
5. Page validation
 Page validation means navigation validation
 We check, can we navigate from one page to other page
 We click on next or back arrow, so, pages should navigate front & back
 We check, pagination (for web based, whether it is navigating on that particular selected
page or not)

6. Graphical User Interface/UI Validation


 This testing test the interface with which user interact directly
 In this test, tester check
1. Display of application
2. Logo & Images- Whether is it clear or blur
3. Alignment
4. Is UI as per wireframe functionality
5. Dropdown behavior
6. Resolution of logo etc.
 This validation of visualization is called GUI validation

 When we performed these sanity testing, if we found blocker/show stopper defects in the
application/feature, then tester will reject the build
 When we performed these sanity testing, if we found defects (buggy build) then we simply
reject the build (ex. we found more than 25 to 30 defects)
 After sanity testing we decide whether build is stable or unstable
 If we will reject the build then we will inform to the developer throw mail (Outlook
Mail) (JIRA/HPALM)
 Then developer will fix the issue/defects & sent us a New build, then tester will perform
again sanity testing
 Ex. Paytm - Recharge module- US- Browser plane information  Developer will coding/
preparing the new build(V.9.0)  Developer will sent for Testing  Tester will do Sanity
Testing (check build stability)  If core functionality not working  If we found a
defect  Tester direly reject the build (V9.0)  Inform to developers by sent a mail &
Developer will fix the defect & prepared a new build (V9.1)  New build (V9.1) will
sent for testing  Tester will do again sanity testing New build (V9.1)
 In sanity testing, we found issue/ defects  Core functionality is not working, System
hang out problem, Run time problem, Pop/link is not working, Environment
problem, etc.
 In sanity testing, Tester will required only 2 hr to 4 hr for the Testing
 In sanity testing, Tester are not writing the Test cases

Note

 When we decide build is unstable then, we send mail to the development lead, test lead
(CC of mail), developer, Product owner (CC of mail)
& scrum master (CC of mail)

Mail
1. Sanity has been performed successfully & these are my observations
2. During sanity, I have found this much defects
3. I have raised that defect & I have assigned it to the developer also
-Defect ID:-
-Comment:-
Expected behavior:-
Actual got behavior:-
-Screenshots
 On this report, actually decide, next testing has to continue or does not
 If we discard the build, then DL, TL & sanity tester & developer sit together & discuss the
issues / defects / show stoppers/ blocker

You might also like