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

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 will be prepared by Testing Head -TH
 Test policy documents defines objective of the project (How much revenue we can
generated from the Testing)
 Test policy documents it is Company Level document
Test Strategy-
 In Test strategy stage Test Strategist (TS) & PM will work
 In Test strategy defines strategy/ approaches against the project (Ex. Automation- Java
langue’s + Selenium tool)
 Test strategy documents it is Company Level document

Test Methodology-
 In Test methodology stage PM will work
 In Test methodology defines on different stages / environments which testing we can
performed
 In Test methodology stage PM will prepared TRM (Test responsibility matrix)

TRM (Test responsibility matrix)-

 TRM mapping development & Testing
 TRM will prepared by PM
Development Information Design Coding Testing Support
Stage gathering/
Analysis
Testing stage

GUI/ UI No No Yes Yes Yes

System & No No Yes Yes Yes
Function
Performance No Yes Yes Yes Yes
Testing

Test Plane-
 In Test Plane stage Test lead will work
 Test Plane documents it is Project Level document
 Test plane documents defines resource (Tester/ Environments), resources allocation,
Job allocation, estimation, etc

Identify Test Scenario/ Case-

 Tester will identify test scenario and design the test cases against these
 Test scenario documents it is Project Level document
 Test scenario / Test cases design against the US

Test cases execution & defect report-

  When developer sent build to Tester then TCE
 While doing the if we found defect then we will inform developer
 Test cases execution & defect report documents it is Project Level document

Test Summary Report/ Test closer report-

 Test summery report against every Sprint
 Test summery report will contains, for every US how many TCD, how many TCE, how
many TCS & how defect found, etc

Software Testing Life Cycle (STLC) –

Q. What is your organization Test process OR what is STLC?

Test Initiation Test Plane Test Scenario

Requirement Test Case Test Case Defect

Analysis Design Execution- sent to
Test Proof developer

Test Summery
Report / Test
Closer

Test Initiation-

 In my organization, test will start with Test initiation

 In Test initiation stage PM will prepared TRM documents
 TRM documents will sent to Test lead


Test Plane-

 In Test plane, Test lead working

 In Test plane, Test lead check Resource (Tester/ Environment), Resource allocation,
Estimation
  Test planes will contains, When to test, What to test, How to testing & Who will test
 The prepared of Test planes is to decide start date and end date of testing activity

Indentify Test Scenario & Test cases design-

 Test scenario defines way to test the Functionality/ application

 Test cases defines step to follow the functionality Or to performed steps for checking
the Functionality of the application

Test Case Execution-

 After completion of TCD, tester will start the execution

 When developer will sent the build then tester will start the TCE
 In TCE, if we found issue/ defects the inform to developer throw Mail (JIRA/
HPALM)
 When developer fix the defect, then tester will do Re-testing & Regression testing
 In TCE, Tester will prepared Test Proof

Test Summery Report / Test Closer-

 In Test summery report- Every US –TCD, TCE, TCE, No. of defects found
 In Test closer – Final report against the Module, which prepared by Test lead
 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 (New Build)

Level 1 BBT/ System & function testing

(If found defect sent to developer)

Level 2 Regression testing on (Modified built)

Level 3 Final Regression Testing

Test Plane-
 Test plane that will be prepared by Test lead
 While preparing the Test planes there parameter focus
1. Resource allocation
2. Job allocation
3. Estimation
4. Main purpose of Test planes to decide Start date and end date of testing

 Test planes will contain-

1. Test plane ID
2. Testing item
 3. Feature to be tested
4. Feature not to be tested
5. Test pass/ Fail criteria
6. Test deliverable (Before TCE  TCD)/ (Unit testing  Deployed build)
7. Test environment
8. Testing task/ US
9. Defect management/ status
10. Staff Training
11. Roles & responsibility
12. Signature & Approval

Entry & Exist criteria-

 Coding  Unit testing  Integration Testing  BBT testing  UAT Testing

 Entry criteria of integration testing- After completion of unit testing
 Exist criteria of integration testing  Completion of integration is exist criteria OR
Entry criteria of BBT testing

Interview question –

1. How your originations testing process ? Or what is STLC?

2. What are different level of Testing
3. What is difference SDLC & STLC
4. What is a Test plane? How you involved in test planes?
5. What test planes will contains
6. What is Entry criteria of unit testing & Exist criteria of integration testing
Test Scenario & Test Case-

SRS/ FRS

Use Case/
User Story Test
Scenario Test cases

BA BA Tester Tester

SRS & Use case-

SRS/ FRS-
 SRS defines as software requirement specification/ functionality requirement
specification
 SRS defines functionality requirement to be development & system requirement that will
be used
 SRS will be prepared by BA
 SRS will be derived from BRS
 SRS will contains
1. Functional requirement
2. Functional flow diagram
3. Use case
4. Screenshot
 Ex. SRS document will be papered for a module (ex. SRS will contains 25 use case)

Use case-
 Use cases defines specific single requirement
 In Agile Use cases are called User story
 Use cases will prepared by BA
 Use cases will be derived from SRS
 Use case will contain
1. Description – detail about the Use cases/ User story
2. Acceptance criteria - Does & Don’t about the US
 Ex. Paytem- Fasttag – Use Case- Fasttage for 4 wheeler vehicle
Test scenario-

 Test scenario derived from User story

 Test scenario defines possible ways to test the functionality of the application
 Test scenario defines “What to test”
 Test scenario will be prepared by Tester
 Test scenario defines high level test cases
 Against one Test scenario, multiple test cases are present
 Test scenario always writes in “+ve way”
 Ex. US - Login Page – Username, Password & Submit button. Username should accept
mobile no. and email id & password should accept combination of 4 to 6 charter

Username-

Password-

Submit

 Test scenario-
1. Verify username text box by passing mobile no. in login page
2. Verify username text box by passing email id in login page
3. Verify password text box by passing comabination4 to 6 charter in login page
4. Verify Submit button functionality in login page

Test cases-

 Test cases derived from Test scenario

 Test cases defines step to test the functionality of the application
 Test cases defines “How to test”
 Test cases will be prepared by Tester
 Test cases defines Low level test cases
 Test cases steps will contains Input, Process & output
 Test cases always writes in “+ve way” & “-ve way”
 Ex. Test scenario- Verify username text box by passing mobile no. in login page
 Ex. Test cases-
 1. Verify username text box by passing Airtel mobile no. in login page
2. Verify username text box by passing VI mobile no. in login page
3. Verify username text box by passing JIO mobile no. in login page
4. Verify username text box by passing BSNL mobile no. in login page
5. Verify username text box by passing MTNL mobile no. in login page
6. Verify username text box by passing by invalid Airtel mobile no. in login page
7. Verify username text box by passing by invalid JIO mobile no. in login page
8. Verify username text box by passing by invalid VI/BSNL/MTNL mobile no. in login
page
9. Verify username text box by passing by Null/ Blank mobile no. in login page
10. Verify username text box by passing a charter into mobile no. filed in login page

 Ex. Test scenario - Verify username text box by passing email id in login page
 Ex. Test cases-
1. Verify username text box by passing @gamil.com id in login page
2. Verify username text box by passing @yahoo.com id in login page
3. Verify username text box by passing @hotmail.com id in login page
4. Verify username text box by passing @outlook.com id in login page
5. Verify username text box by passing @rediffmail.com id in login page
6. Verify username text box by passing @company.com id in login page
7. Verify username text box by passing invalid @gamil.com id in login page
8. Verify username text box by passing invalid @yahoo.com/ @hotmail.com id in login
page
9. Verify username text box by passing null/blank @gamil.com id in login page

 Ex. Test scenario - Verify password text box by passing comabination4 to 6 charter in
login page
 Test cases –
1. Verify by passing Abcdef charter into password text box in login page
2. Verify by passing ABcdef charter into password text box in login page
3. Verify by passing ABCdef charter into password text box in login page
4. Verify by passing ABCDef charter into password text box in login page
5. Verify by passing abcdEF charter into password text box in login page
6. Verify by passing abCDef charter into password text box in login page
7. Verify by passing @abcde charter into password text box in login page
8. Verify by passing abcd@ charter into password text box in login page
9. Verify by passing abc@de charter into password text box in login page
10. Verify by passing ab@ charter into password text box in login page
11. Verify by passing abcdefsgrhf@ charter into password text box in login page
 12. Verify by passing null/blank charter into password text box in login page

Test Cases-
 In my project, Test cases we will writes in the excel sheet
 Excel sheet fields
1. Test cases ID
2. Priority
3. Reference
4. Test scenario/ Title
5. Pre-request/ Pre-condition
6. Test data
7. Test cases
8. Test cases steps / Step of test cases
9. Expected result
10. Comments/ Suggestion
11. Actual result
12. Pass/ Fail Criteria
13. Defect ID

 Test cases will be written based on some logic

1. Functionality/ US description & acceptance criteria related test cases
2. Business logic related test cases
3. Input domain related test cases
4. GUI/ UI related test cases
  US- User Story- 30074- Login for VCTC staff & student

Description Acceptance criteria

Login page of VCTC application Username text box accept only mobile no. Existing in
contains Username text box, password your domain (vctc student & staff)
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 mobile number (error message- enter valid data)
VCTC student & staff only login, Username text box shows the error for invalid mobile
from which they login into their no. (error message- Check entered mobile no.)
VCTC account page. Login page will Password should contains char of 6 to 8
contains all page as per standard color Password text box will accept One Capital letter, One
as suggested. Small letter, One special char, One number
Password text box will masked
vctc page- Password text box doesn’t accept combination other
172.10.20.132:8080/vctc.com than One Capital letter, One Small letter, One special
char, One number these (error message- enter valid
data)

Test scenario-Verify by passing mobile no. into Username text box of VCTC login page
Test cases-
1. Verify by passing 9 series mobile no. of student & staff into Username text box of VCTC
login page
2. Verify by passing 8 series mobile no. of student & staff into Username text box of VCTC
login page
3. Verify by passing 7 series mobile no. of student & staff into Username text box of VCTC
login page
 4. Verify by passing 6 series mobile no. of student & staff into Username text box of VCTC
login page
5. Verify by passing 9 digit mobile no. into Username text box of VCTC login page
6. Verify by passing 11 digits mobile no. into Username text box of VCTC login page
7. Verify by passing other mobile no. of student & staff not belong to vctc domain into
Username text box of VCTC login page
8. Verify by passing null/ blank into Username text box of VCTC login page
9. Verify by passing charter/ String into Username text box of VCTC login page

Test scenario -Verify by passing combination of 6 to 8 charter into Password text box of VCTC
login page

Test cases-

1. Verify by passing 6 charter combination into password text box  6 charter combination
should be accepted in Password filed
2. Verify by passing 7 charter combination into password text box  7 charter combination
should be accepted in Password filed
3. Verify by passing 8 charter combination into password text box  8 charter combination
should be accepted in Password filed
4. Verify by passing 5 charter combination into password text box  5 charter combination
should not be accepted in Password filed and error message - enter valid data
5. Verify by passing 9 charter combination into password text box  9 charter combination
should not be accepted in Password filed and error message - enter valid data
6. Verify by passing null/blank values into password text box  Null/blank combination
should not be accepted in Password filed and error message - enter valid data
7. Verify by passing 6 charter combination all special charter into password text box  6
charter combination all special charter should not be accepted in Password filed and error
message - enter valid data
8. Verify by passing 6 charter combination all Capital charter into password text box  6
charter combination all Capital charter should not be accepted in Password filed and error
message - enter valid data
9. Verify by passing 6 charter combination all Small charter into password text box  6
charter combination all small charter should not be accepted in Password filed and error
message - enter valid data
10. Verify by passing 6 charter combination all Number charter into password text box  6
charter combination all Number charter should not be accepted in Password filed and
error message - enter valid data
 11. Verify by passing 6 charter combination will contains Number, Capital & Small letter
into password text box  These combination of Number, Capital & Small letter should
not be accepted in Password filed and error message - enter valid data
12. Verify by passing 6 charter combination will contains Special, Capital & Small letter into
password text box  These combination of Special, Capital & Small letter should not be
accepted in Password filed and error message - enter valid data

Test scenario-Verify by functionality of sing in button of VCTC login page

Test case-

Test cases for following things-

1. Pen, Chair, Fan, Watch, Bottle, Laptop, Mobile, etc

2. Whatup, Facebook, Instgram, Flipkart, Amazon, etc
3. Scenario based Test cases – Consider a admission page for 12th collages, Loan
calculator / EMI calculator

Go to - https://artoftesting.com/chair
Test cases for the PEN-

 Test cases for Pen

 Test scenario-
1. Verify GUI/UI of the Pen
2. Verify the material/ dimension/ body of the Pen
3. Verify the Refill of the Pen
4. Verify the writing functionality of the Pen
 Test cases-
1. Verify the pen visibility ER – Some pen should visibility
2. Verify the outer & cap color of the pen
3. Verify the logo present in the pen
4. Verify the brand name on pen
5. Verify the text on pen
6. Verify the material body of the Pen
7. Verify the material Cap of the Pen
8. Verify the material Refill of the Pen
9. Verify the material grip of the Pen
10. Verify the material nib of the Pen
11. Verify the dimension/ length/size/weight of the Pen
12. Verify the dimension/ length/size/ weight of the Cap
 13. Verify the dimension/ length/size/ weight of the Refill
14. Verify the dimension/ length/size/ weight of the nib
15. Verify Refill types of the Pen
16. Verify ink present in Refill of the Pen
17. Verify color of ink present in Refill of the Pen
18. Verify Viscosity of ink present in Refill of the Pen
19. Verify ink present in Refill of the Pen
20. Verify life of ink present in Refill of the Pen
21. Verify quantity of ink present in Refill of the Pen
22. Verify leakages of ink present in Refill of the Pen
23. Verify reusable Refill of the Pen
24. Verify the writing capacity of the Pen
25. Verify the writing capacity of the Pen on white paper with black ink
26. Verify the writing capacity of the Pen on black paper with black ink
27. Verify the writing capacity of the Pen on stone with black ink
28. Verify the writing capacity of the Pen on wood paper with black ink
29. Verify the writing capacity of the Pen on rough surfaces paper with black ink
30. Verify the writing capacity of the Pen against anti gravity
31. Verify the writing capacity of the Pen in water on a paper with black ink
32. Verify the writing capacity of the Pen on black paper with black ink
33. Verify the writing capacity of the Pen with high tempture and low tempture with
black ink
34. Verify the writing capacity of the Pen high allitutude with black ink
35. Verify the writing capacity of the Pen with two refills
36. Verify the writing capacity of the Pen with three refills
37. Verify the writing capacity of the reusable Pen
38. Verify the writing capacity of the use and throw Pen
39. Verify the button on the Pen
40. Verify the button on the Pen

Test cases for the Whatup-

 Test cases for Whatup

 Test scenario-
1. Verify group chatting messages on whatup
2. Verify advance feature chatting messages of group in whatup
3. Verify types of media and feature chatting of group in whatup
4. Verify text on chatting of group in whatup
 Test Case-
 1. Verify message color , Time & Tick present in group chatting message
2. Verify message color , double Tick present in group chatting message
3. Verify chatting present in both mobile and laptop
4. Verify mention chatting present in group chatting message
5. Verify message display position in group chatting message
6. Verify message if internet is not on in group chatting message
7. Verify message if internet is slow in group chatting message
8. Verify advance feature present in group chatting message
9. Verify Message info advance feature present in group chatting message
10. Verify Reply advance feature present in group chatting message
11. Verify Forward advance feature present in group chatting message
12. Verify start functionality in Forward advance feature present in group chatting
message
13. Verify Delete functionality in Forward advance feature present in group chatting
message
14. Verify Delete for me/ Delete for everyone/ cancel functionality in Forward advance
feature present in group chatting message
15. Verify advance feature after Delete for me/ Delete for everyone functionality in
Forward advance feature present in group chatting message
16. Verify Star advance feature present in group chatting message
17. Verify messages and Undo button in Star advance feature present in group chatting
message
18. Verify Delete functionality in Forward advance feature present in group chatting
message
19. Verify attachment types feature present in group chatting message
20. Verify Contact attachment types feature present in group chatting message
21. Verify Documents attachment types feature present in group chatting message
22. Verify Camera attachment types feature present in group chatting message
23. Verify Photo & attachment Media types feature present in group chatting message
24. Verify Emoji Media types feature present in group chatting message
25. Verify GIF Media types feature present in group chatting message
26. Verify Sticker Media types feature present in group chatting message
27. Verify Vocie Media types feature present in group chatting message

Test Cases for Loan Page-

1. Verify GUI/UI of Home loan Amount/ Interest Rate/ Loan Tenure
2. Verify GUI/UI of Home loan Loan EMI/ Total interest payable/ Break-up of total
payment
3. Verify values passed in Home loan Amount text box
4. Verify min and maximum values passed in Home loan Amount text box
5. Verify by passed string / charter in Home loan Amount text box
6. Verify by passing special charter values passed in Home loan Amount text box
7. Verify by values decimal / fractional values passed in Home loan Amount text box
8. Verify gadget / wedges position after passing Integer values in Home loan Amount text
box
9. Verify gadget / wedges position after passing -ve values, Charter, String, Decimal values
in Home loan Amount text box
10. Verify home load amount text box after moving gadget / wedges in specify values
11. Verify home load amount text box after moving gadget / wedges in min values
12. Verify home load amount text box after moving gadget / wedges in Max values
13. Verify home load amount text box after moving gadget / wedges in min values
14. Verify after changing both home load amount text box and moving gadget / wedges in
some values
15. Verify amount unit of a home load amount text box
 16. Verify values passed in Interest Rate text box
17. Verify min and maximum values passed in Interest Rate text box
18. Verify by passed string / charter in Interest Rate text box
19. Verify by passing special charter values passed in Interest Rate text box
20. Verify by values decimal / fractional values passed in Interest Rate text box
21. Verify gadget / wedges position after passing Integer values in Interest Rate text box
22. Verify gadget / wedges position after passing -ve values, Charter, String, Decimal values
in Interest Rate text box
23. Verify Interest Rate text box after moving gadget / wedges in specify values
24. Verify Interest Rate text box after moving gadget / wedges in min values
25. Verify Interest Rate text box after moving gadget / wedges in Max values
26. Verify Interest Rate text box after moving gadget / wedges in min values
27. Verify after changing both Interest Rate text box and moving gadget / wedges in some
values
28. Verify amount unit of a Interest Rate text box

29. Verify PI chart of a Break-up total amount payable

30. Verify PI chart of a Break-up total amount payable after changing Home Loan amount
31. Verify PI chart of a Break-up total amount payable after changing Interest rate
32. Verify PI chart of a Break-up total amount payable after changing Loan tenure
33. Verify PI chart of a Break-up total amount payable after changing Loan tenure and
keeping fix values of Home Loan amount, Interest rate
34. Verify PI chart of a Break-up total amount payable after changing Home Loan amount
and keeping fix values of Loan tenure, Interest rate
35. Verify PI chart of a Break-up total amount payable after changing Interest rate and
keeping fix values of Loan tenure, Home Loan amount
36. Verify calculation of PI chart of a Break-up total amount payable

Test cases review-

 Review- Review is nothing checking the correctness & completeness of the
documents
 4 types review
1. Self Review
 2. Peer review
3. Internal review
4. External review

 Tester should have to complete the test cases design

1. Self Review-
 When tester will write the test cases then tester itself do the review these review called
self review
 In my project, Self review done by Test lead only

2. Peer review-
 When tester will write the test cases then seniors tester/ colleague/ Test lead do the
review these review called peer review
 Tester will sent the Mail to the seniors tester/ colleague/ Test lead for peer review

3. Internal review-
 When tester will write the test cases then these test cases will be review by BA
 Tester will sent the Mail to the BA for Internal review
 Tester will set up a meeting with BA for internal review

4. External review-
 When tester will write the test cases then these test cases will be review by Client/ UAT
team
 External review meeting will be set up by test lead
 Test lead will start the meeting & individual tester will review the test cases
 External meeting involved- Test lead, Client/ UAT Team, Tester, Developer

 In my project, we will conduct Internal / External review/ Peer Review

 In review, if we got any comments/ Suggestion in test cases review then Tester will
accept the comments/ Suggestion, these we will writes in comments/ Suggestion
column of test cases excel.
 Test cases will be modified according comments/ Suggestion. Mail to Test Lead/ BA/
UAT Team.

Test cases review which consider parameters-

 In Test cases review focus

1. Test cases should be cover US/ Business related
 2. Test cases should be cover all functionality (end to end)
3. Test cases should be cover UI/GUI
4. Test cases should not be duplicated
5. Test cases should in proper format
6. Test cases should be simple & Understand
7. Test cases spelling mistakes
8. Test cases grammar mistakes

Traceability Matrix-
 Traceability matrix against the Test case & defect for a US/ requirement
 Traceability matrix defines linking or mapping against the Test cases & defect with
US
 Traceability matrix are 2 types
1. Forward Traceability matrix
2. Backward Traceability matrix
1. Forward Traceability matrix-
 Test cases will be linked or mapped with US/ requirement
 Test cases we will writes in excel sheet, these excel sheet we will link or attached with
the US, it is called forward traceability matrix
 Forward traceability matrix will prepared in (Test cases will be linked or mapped with
US) in JIRA/ HPALM

2. Backward Traceability matrix-

 In TCE if we found defects the these defects will be linked or mapped with US
 Backward traceability matrix defines defects will be linked or mapped with US
  Backward traceability matrix prepared with JIRA/ HPALM

Test cases execution-

 In TCE, tester will prepared Test proof
 Test proof  Test cases & Screenshot are present in test proof

Defect life cycle-

 Defect defines error in the application while doing the testing.
 In TCE, if we found d defects then we will raised to the developer
 Defects different status/ stage – New, Open, Fix, Re-open, Rejected, Closed, Differed, etc
 Defect life cycle- The journey of defects from their life cycle OR New to Closed status

Closed

Fix
Re-open

New Open Rejected

Differed
 Tester Developer Developer Tester

 New- When tester will found error in the application, then he will raised the
defect. Defect will raised in JIRA/ HPALM and Tester will mail to developer
throw JIRA/ HPLAM
 Tester will mark defects status as New in JIRA/ HPALM
 Open- When developer is working or analysis on the defects, developer will mark
defect status as open
 Fixed- When developer found that defects is valid then he fix the defects and
developer will mark defect status as Fixed
 Developer will mail to Tester throw JIRA/ HPLAM
1. Closed- In fixed defects tester will do re-testing and regression testing. If
defects has been fixed. Tester will mark defect status as Closed
 Tester will mail to developer throw JIRA/ HPLAM
2. Re-open - In fixed defects tester will do re-testing and regression testing. If
defects has not fixed. Tester will mark defect status as Re-open
 Tester will mail to developer throw JIRA/ HPLAM

 Rejected- When developer is found that defects is invalid in doing analysis/

working on the defects. Developer will mark defect status as Rejected.
 Developer will mail to Tester throw JIRA/ HPLAM
 Differed- When developer is not fixing the defects in current sprint. Differed
defects occurred due to
A. Defects priority is very less
B. Developer has another work for priority
C. Developer is not present Or defects will take more time for the fixing
 In my project, Differed defects status will be decided by PM, BA & designer

 Duplicate defects-
 Duplicate defects is nothing same/ similar defects we will raised again
 Ex. Paytm- BSNL mobile no. is not accepting for all state – Defect ID - 1002
 Ex. Paytm- BSNL mobile no. is not accepting for Maharashtra state – Defect ID –
1003 (Duplicate defects)
  Ex. Paytm- BSNL mobile no. is not accepting for MP state – Defect ID – 1004
(Duplicate defects)

 Re-producible defects-
 Re-producible defects/ know defects defines, defects which is produce again and
again in the testing
 Re-producible defects occurred due
1. Environment problem i.e. some functionality not support in SIT environments.
2. Database connectivity problem
3. Deployment process (Developer deployment into SIT environment)

 Re-producible defects maintain in JIRA/ HPALM tool (Re-producible – Y/N)

 Show stopper defects/ Blocker defect-

 Defect which is stop the testing. Ex. While doing testing if core functionality of the
Application is not work
 Ex. Paytm – Recharge module- Mobile no. is not accepting

 Bug /defects leakage-

 Bug/ Defect leakage defines defects which is missed from SIT environment to UAT
environment

 Bug released- Application we will deploy or delivery to client with knows defects.
Defects Priority & Severity should very low

 Defect density- Number of defects found in a specific US/ Module

Defect raised field-

 Defect will raised in JIRA/ HPALM tool
 Field present while creating defects in JIRA/ HPALM tool
1. Summery* – Short Description about defects
2. Description – Steps to produce the defects
3. Created By* – Tester Name
4. Created date – System date
5. Assigned to* – Developer name
 6. Status* – Values present in drop down New, Open, Fixed, Re-open, Closed, Rejected
7. Priority – Very high, High, Medium, Low
8. Severity* - Critical, High, Medium, Low
9. Re- produce – Y/ N
10. Sprint/ US link –
11. Attachment – Screenshot of the defects

 Manual Testing – module 400 TCD  Regression suit – 40 to 50

Report-
 In my project, we have following report-
1. Test cases execution/ Test proof  Tester
2. Defect report/ Bug report  Tester
3. Test summery Report  Test Lead (Tester help for to Test Lead)

4. Test Closer report  Test Lead

Defect report/ Bug report –

 Defect report will prepared by tester for every Sprint

Test summery Report-

 Test summery report – TCD, TCE, TCS & no. of defects found in US for every Sprint
Test closer report-
 Test closer report prepped by Test lead  Module against test sing off documents

Interview question-
1. What is Test plane? Have you involved in Test Plane prepared?
2. What is test scenario & Test cases?
3. What is User story & Use Case?
4. On which parameter, you will consider while writing test cases?
5. Writes the test cases for things? Object- Pen, scenario based test cases
6. What are the field present while writing the test cases
7. What are different types of Review? And how you are conducting?
8. If you got suggestion in test cases review? How you take care of these?
9. What is traceability matrix and where you will prepped
10. What is defect life cycle?
11. What is duplicate & re-producible defect?
12. What is a show stopper defect?
13. What are different report you are preparing in you project?

Real Interview question-

1. Who will do deployment?

2. What is approached when developer is not accepting the defect?
3. What is roles & responsibility in your project?
 Answer- In my project, my roles & responsibility
1. Requirement analysis/ understand – Grooming meeting
2. Identify test scenario
3. Test cases design – Excel sheet
4. Test cases review – Internal / external review
5. Test cases execution – Test proof
6. Defect report –
7. Test summery report- (Help to Test lead)
8. Client interaction (Sprint review meeting)
 9. Daily stand up/ Scrum meeting

4. When you know that testing is completed?

 Answer-
1. All Test cases should be executed
2. All defects should be fixed
3. Tractability matrix should be complete

5. What problems you have faced in you last project? OR what problem you have
faced in your testing carries?
 Answer- In testing
 If we have less domain knowledge about the project
 If we have less resource is the project
 If we have the environment problem
 If developer is not communicated properly
 Client Frequent changes in the requirement
 If we have less test data for testing
 If developer is not informing while doing deployment

6. How many test cases you will write per & how many will execute?
 Answer- Test cases design it is totally depending on US or functionality
 An a average, I will write 25 to 30 test case per day
 An a average, I will execute 15 to 20 test cases per day
 An a average, I will writes test script 4 to 5 per day in automation

7. How many test cases you will write per & how many will execute?
 Answer- I have written many test case in my last project
 I know exact number but I rember as I have Test cases No- 145 to 265

 1 Year = 24 to 25 Sprint
 1Sprint = 3 to 4 US
 1US = 25 to 30 test cases
8. How many defect you will raised per day OR per US?
 Answer- It totally depends on the test cases execution and coding of the developer
 If developer will done more mistake or error in coding then we get more defect
 If developer will done less mistake or error in coding then we get less defect
 An a average, I will raised 4 to 5 defects per US/ day

9. What is your approach, if environments defect found in SIT & not found in Dev?
 Answer- When tester, found a defect in SIT then we will raised/ create defect in JIRA/
HPALM with screenshot & mail to developer
 Developer says to is not a defect and he will take call with tester. For showing casing the
defect which is not present in Dev environments
 SO in call Tester will shows case the defect in SIT environments?
 Defect occurred in SIT due to–
1. Deployment process
2. Due to Cash & cookies in the browser  Tester will clear the cases & cookies and
Testing OR Test the application in “Incognito Window”

 In daily stand up, we will raised these issue to PM & designer

10. What is your daily routine?

 Answer- We have office timing at 9 to 6 pm
 I will login to office at 9 am, then we will Mail (outlook) and we stand up at 9.45 am to
10 am
 In daily Stand, we will discussed work progress & I will get today’s work
 I will start my work after  Test cases design or Test case execution
 Evening daily stand up- What works we have done today’s.

11. How many test cases are present in your regression suite?
 Answer- Manual Test module- 30 US
 1 US = 25 to 30 TCD
 Overall total manual Test cases = 30 * 30 = 900 TCD
 Automation Regression suite = 180 or 200 Test cases

12. Where we got the log after getting error/defect/issue in the application? OR Where
we got the log
 Answer- In my project, while doing the testing, if we got error in application. Then we
will get these log in workbook (Team channel-Project against error)
 If we openwork book then we will indentify where is the problem in the application/
functionality