Test Documentation –

Q. What is your organization Test documentation?

 Test Document hierarchy

Quality control – QC/ Test Policy

Testing Head -TH Company Level
document
Test Strategist – TS & PM Test Strategy

Project manager – PM Test Methodology TRM

Team Lead – TL Test Plane

Identify Test Scenario/ Case

Test Procedure/Design
Tester – Tester Project Level
Test Script/ Execution document
(Test Proof)

Defect Report

Test Summary Report

Team Lead – TL
Final Report/ Test
closer Report

Test Policy-
 Test policy documents defines objective of the project (Project renew generated)
 Test policy documents prepared by Testing Head -TH
 Test policy documents company level documents
Test Strategy-

 Test Strategy defines which Strategy/approaches we can apply for full fill the objective of
the project
 Ex. Project  Automation testing  Java/ C#/ Python / etc + Selenium tool
 Test Strategy documents will be prepared by Test Strategist – TS & PM
 Test Strategy documents company level documents

Test Methodology-

 Test methodology defines  Environment follow/use for Strategy/approaches

 Test methodology documents will be prepared by PM
 Test methodology documents Project level documents
 Test methodology documents  PM will prepared the TRM (Test responsibility
matrix)
 TRM defines development stage mapping with testing factor
 While preparing the TRM consider
1. Project requirement
2. Project scope
3. Risk in project

Development Information Design Coding Testing Maintains

Stage gathering/
Analysis
Testing
factor
System & No No Yes Yes Yes
functional
Testing
Security No No No Yes Yes
Performance No No No Yes Yes
Testing

Test Plane-

 Test plane will contains Resource allocation, Job allocation, estimation, etc
 Test plane documents prepared by Test lead
 Test plane documents Project level documents

Identify test scenario & Test case design –

 Tester will identity test scenario & Test cases design

  Test scenario & Test cases design prepared by Tester
 Test scenario & Test cases documents Project level documents

Test cased execution & defect report-

 In TCE, if we found defects then we will raised to developer

 Modified build we will perform regression & Retesting.

Test summery report & Test closer report-

 Test summery report will contains TCD, TCE & Test cases skip, ect
 Test summery report & Test closer report prepared by Test lead
 Test summery report & Test closer report documents Project level documents

Software Testing Life Cycle (STLC) –

Q. What is your organization Testing process?
Q. What is STLC?

Test Initiation Test Plane Test Scenario

Defect
Test Case
Test Case sent to
Requirement Analysis Execution-
Design developer
Test Proof

Test Closer/ Test

Summery Report

Test Initiation-

 In Test initiation, PM is work

 In Test initiation, PM will prepared TRM (Test responsibility matrix)
 TRM documents will contains mapping between development & Testing stage

Test Plane-

 In Test plane stage, test lead will work

  Test lead will prepared test plane
 These test plane will contains Resource allocation, Job allocation & Estimation
 Test plane contains  What to test, who will test, when to test & How to test

Test Scenario & TCD-

 When US assignee to Tester then tester will first identify Test Scenario
 After identify Test Scenario tester will prepared a Test cases design

Test cases execution & defect-

 After completion of Test cases design, when we got the build

 Tester will start the Test cases execution
 In TCE, if we found defects then we will raised a defects to developer & inform to throw
mail
 When developer will fix these defect, tester will do re-testing & regression testing

Test summery report/ Test closer-

 In Test summery report will contain, for every US how much TCD, TCE, TCS & defect
 Testing Process-

BRS
Development Testing
SRS/FRS/CRS

Design Test Initiation Stage

Coding Test Plane

STLC
SDLC Unit Testing Test Case Design

Integration Testing Test Case Execution & Closer

(Install Build)

Level 0 Sanity/ Smoke Testing (Check the Stability of build)

Level 1 BBT/ System & function testing (Intern & External)

(If found defect sent to developer) (Inform throw JIRA/TFS)

Level 2 Regression Testing on Modified built

Level 3 Final Regression Testing

Test Plane-
 Test plane will prepared by test lead
 While doing Test plane, test lead focus on following parameter
1. Resource allocation
2. Job allocation
3. Estimation

Test plane contains-

1. Test plane ID
2. Team items
3. Feature to testing
 4. Feature not be to testing
5. Test pass/ Fail
6. Test delivery (TCD completed Start BBT)
7. Test environments
8. Defect life cycle
9. Testing task
10. Staff training
11. Roles & reasonability
12. Approval & Signature

Test Scenario-

SRS/ FRS/ CRS

User Cases/ US

Test scenario

Test Cases
Design

BA BA Tester Tester

SRS/ FRS/ CRS-

 SRS will defines, software requirement to be developer & system required to be used
 SRS derived from BRS
 SRS will be prepared by BA
 SRS contains
1. Functional requirement
2. Functional flow diagram
3. Use cases
4. Screenshot
 SRS will contains multiple User Case
Use Case-
 Use Case will defines Functional / Single specific requirement
 Use Case derived from SRS
 Use Case will be prepared by BA
 Use Case contains
1. Description
2. Acceptance criteria
 Use Cases will contains multiple User stories

Test Scenario & Test cases-

 Test scenario defines way to test functionality
 Test scenario will be prepared by tester
 Test scenario defines “What to test”
 Against Test scenario, we will contains multiple test cases
 Test scenario always in “+ve ways”
 Test scenario always defines “High level Test case”
 Ex. US – Login Page – Flipkard login page

Test scenario-
1. Verify the login page by passing mobile number
2. Verify the login page by passing email
3. Verify the login page by password
4. Verify the login button functionality in Flipkard login page
Test cases-
 Test cases defines how to test functionality
 Test cases will be prepared by tester
 Test cases defines “How to test”
 Against Test cases, we will contains input, process & result
 Test cases always in “+ve ways & -ve ways”
 Test cases always defines “Low level Test case”
 Ex. US – Login Page – Flipkard login page

Test scenario- Verify the login page by passing mobile number

Test cases –
1. Verify the login page by passing BSNL mobile number
2. Verify the login page by passing VI mobile number
3. Verify the login page by passing Airtel mobile number
4. Verify the login page by passing JIO mobile number
5. Verify the login page by passing MTNL mobile number
6. Verify the login page by passing invalid BSNL mobile number
7. Verify the login page by passing invalid VI mobile number
8. Verify the login page by passing invalid Airtel mobile number
9. Verify the login page by passing invalid JIO mobile number
10. Verify the login page by passing invalid MTNL mobile number
11. Verify the login page by passing null/ Blank mobile number

Test scenario -Verify the login page by passing email

Test cases –
1. Verify the login page by passing email id (@gmail.com)
2. Verify the login page by passing email id (@yahoo.com)
3. Verify the login page by passing email id (@readiffmail.com)
4. Verify the login page by passing email id (@hotmail.com)
5. Verify the login page by passing email id (@outllok.com)
6. Verify the login page by passing email id (@domain.com)
7. Verify the login page by passing invalid email id ([email protected])
8. Verify the login page by passing invalid email id
9. Verify the login page by passing null/ Blank email id
Test scenario - Verify the login page by password
Test scenario - Verify the login button functionality in Flipkard login page

Test cases-
 Test cases will written against test scenario
 Test cases we will write in the Excel sheet/ Direct test cases are writing in the JIRA/ TFS
 While preparing Test cases, we will focus on
1. Test cases related to business of client/ Functionality related test cases
2. Test cases related to input domain
3. Test cases related to GUI/ UI

User Story- 30074

Description Acceptance criteria
Login page of VCTC application Username text box accept only mobile no. Existing in your
contains Username text box, domain
password text box & sign in button. Username text box will unmasked
Username text box doesn’t accept other then VCTC
This login page will provided for student & staff mobile number (error message- enter valid
VCTC student & staff login, from data)
which they login into their VCTC Password should contains char of 6 to 8
account page. Login page will Password text box will accept these combination One
contains all page as per standard Capital letter, One Small letter, One special char, One
colour as suggested. number
Password text box will masked
Password text box doesn’t accept One special char, One
number these combination (error message- enter valid
data)

Test scenario- Verify the Username text box in vctc login page
Test cases –
1. Verify username text box by passing valid mobile no (BSNL- vctc student/ staff)  EC -
BSNL- vctc student/ staff mobile no should be accepted
2. Verify username text box by passing valid mobile no (JIO- vctc student/ staff)  EC -
JIO - vctc student/ staff mobile no should be accepted
3. Verify username text box by passing valid mobile no (VI- vctc student/ staff)  EC - VI
- vctc student/ staff mobile no should be accepted
4. Verify username text box by passing valid mobile no (Airtel- vctc student/ staff)  EC -
Airtel - vctc student/ staff mobile no should be accepted
 5. Verify username text box by passing valid mobile no (MTNL- vctc student/ staff)  EC -
MTNL - vctc student/ staff mobile no should be accepted
6. Verify values entering into username text box  EC – Mobile no. should be unmasked
7. Verify username text box by passing In-valid mobile no of JIO other than vctc student/
staff  EC – Username text box will shows error – Enter valid data
8. Verify username text box by passing In-valid mobile no of BSNL/VI/ Airtel/ JIO other
than vctc student/ staff  EC – Username text box will shows error – Enter valid data

Test scenario- Verify the Password text box in vctc login page
Test cases-
1. Verify password text box by passing valid combination (Abc@123))  EC = These
combination should be accepted
2. Verify password text box by passing valid combination (aBc@123))  EC = These
combination should be accepted
3. Verify password text box by passing valid combination (a@Bc123))  EC = These
combination should be accepted
4. Verify password text box by passing valid combination (@aBc123))  EC = These
combination should be accepted
5. Verify password text box by passing valid combination (123@Abc))  EC = These
combination should be accepted
6. Verify password text box by passing valid combination (12@34Ab)  EC = These
combination should be accepted
7. Verify values enter in password text box  EC = These combination should be accepted
only 6 to 8 charter
8. Verify values enter in password text box  EC = These combination should masked
9. Verify values enter in password text box  EC = These combination should be accepted
only 6 to 8 charter
10. Verify password text box by passing In-valid combination (1234)  EC = These
combination should not be accepted & error message – enter valid data
11. Verify password text box by passing In-valid combination (ABCD)  EC = These
combination should not be accepted & error message – enter valid data
12. Verify password text box by passing In-valid combination (abce)  EC = These
combination should not be accepted & error message – enter valid data
13. Verify password text box by passing In-valid combination (@#$%)  EC = These
combination should not be accepted & error message – enter valid data
14. Verify password text box by passing valid combination (Ab@1)  EC = These
combination should not be accepted & error message – enter valid data
15. Verify password text box by passing In-valid combination (ABCd@#$abc123)  EC =
These combination should not be accepted & error message – enter valid data
16. Verify password text box by passing null/blank values  EC = These combination
should not be accepted & error message – enter valid data
Test scenario- Verify the Sign in button functionality in vctc login page
Test cases-
1. Verify sing button functionality for valid username (student) & valid password  EC=
For these combination user should go to home page
2. Verify sing button functionality for valid username (staff) & valid password  EC= For
these combination user should go to home page
3. Verify sing button functionality for Invalid username & valid password  EC= For these
combination user should not go to home page
4. Verify sing button functionality for Invalid username & Invalid password  EC= For
these combination user should not go to home page
5. Verify sing button functionality for valid username & Invalid password  EC= For these
combination user should not go to home page
6. Verify sing button functionality for null/blank username & valid password  EC= For
these combination user should not go to home page
7. Verify sing button functionality for valid username & null/blank password  EC= For
these combination user should not go to home page