0% found this document useful (0 votes)
363 views18 pages

Practical 12 - Defect Repport & Test Cases For Gmail Login Page

Uploaded by

st5617067
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
363 views18 pages

Practical 12 - Defect Repport & Test Cases For Gmail Login Page

Uploaded by

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

TEST CASES FOR GOOGLE LOGIN PAGE

TEST CASE ID TEST CASE DESCRIPTION

TC_001 Username should contain a letter, number and period.

TC_002 Username should not be left blank.

TC_003 Username should not be more than 40 characters.

TC_004 Username should not start with or contain any symbols.

TC_005 The password should be at least 6 characters.

The password should contain a combination of letter, numbers,


TC_006
and symbols.

TC_007 The password should not contain spaces and period.


Scenario 1: FOR
LOOP PROGRAM
Scenario 2:
SWITCH CASE
PROGRAM
Check Upper,
Middle ,Lower
Berth
Scenario 3 : DO
WHILE
PROGRAM
Any concession
for Senior Citizen
if applicable
Scenario 4 : IF
ELSE PROGRAM
BUG REPORT FOR GOOGLE LOGIN PAGE

SR NO TEST CASE ID TEST OBJECT TEST DESCRIPTION TEST STEPS TEST DATA EXPECTED RESULT
ACTUAL RESULT PASS
Defect Report Template
ID

Project

Product

Release Version

Module

Detected Build
Version

Summary

Description

Steps to Replicate
Actual Result

Expected Results

Attachments

Remarks

Defect Probability

Defect Severity

Defect Priority

Reported By

Assigned To
Status

Fixed Build Version


Defect Report Template
Unique identifier given to the defect. (Usually, automated)

Project name.

Product name.

Release version of the product. (e.g. 1.2.3)

Specific module of the product where the defect was


detected.

Build version of the product where the defect was detected


(e.g. 1.2.3.5)

Summary of the defect. Keep this clear and concise.

Detailed description of the defect. Describe as much as


possible but without repeating anything or using complex
words. Keep it simple but comprehensive.
Step by step description of the way to reproduce the
defect. Number the steps.
The actual result you received when you followed the
steps.

The expected results.

Attach any additional information like screenshots and logs.

Any additional comments on the defect.

Probability of the Defect.

Severity of the Defect.

Priority of the Defect.

The name of the person who reported the defect.

The name of the person that is assigned to analyze/ fix the


defect.
The status of the defect. (See Defect Life Cycle)

Build version of the product where the defect was fixed


(e.g. 1.2.3.9)
Defect Report Template
ID

Project

Product

Release Version

Module

Detected Build
Version

Summary

Description

Steps to Replicate
Actual Result

Expected Results

Attachments

Remarks

Defect Probability

Defect Severity

Defect Priority

Reported By

Assigned To
Status

Fixed Build Version


Defect Report Template

You might also like