Scribd
Upload
53 views6 pages

Test Scenario ID Importance

The document contains test scenarios for validating login and communication functionality. It lists 5 login test scenarios with different importance levels and 5 communication test scenarios. It also describes the test scenarios, defines importance levels, and outlines the testing process including test environments, types of testing, roles, and timing.

Uploaded by

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

Test Scenario ID Importance

The document contains test scenarios for validating login and communication functionality. It lists 5 login test scenarios with different importance levels and 5 communication test scenarios. It also describes the test scenarios, defines importance levels, and outlines the testing process including test environments, types of testing, roles, and timing.

Uploaded by

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

Test scenario document

Test scenario ID Importance


GM_LOGIN_001 High
GM_LOGIN_002 medium

GM_COM_001 medium
GM_COM_002 medium
GM_COM_003 medium
GM_COM_004 low
GM_COM_005 high

Low
Medium
high
Test scenario description
validate if the user is logged in successfully when he enters the right user name and password
validate if the user is login fails when credentials are incorrect

Validate if the user is able to write in the space provided for the email
Validate if the user is able to send an email without the subject field
Validate if the user is able to send an email without any names/addresses in the to/cc/bcc fields
validate if the user can send an email with just CC or BCC
Validate if the attachment exists when the email body contatin "attachment" word

does not disrupt the working of the site, cosmetic


requirements when not met will not result in complete dysfunction
a requirement that has to be mandatorily met
Test cases -
1
4
Environments

White box testing Unit testing Dev enviroment

Integration Testing Dev environment

Black box testing System testing QA environment

UAT- user acceptance


testing QA environment

QA environement/developers
Alpha environment

User's environment/production
Beta environment
What does this involve? Who? When?

Checking the code- A unit of code is


programming logic Developers developed and is ready

When the units of code


Checking the combination of 2 involved in a certain
or more units of code to see if integration feature are
they interface correctly Developers developed

When the finished


Checking the features of the code/build is deployed
software QA team in the QA environment

Checking the system - by the


users to see if their End users- power users/ When system testing is
requirements are met Qa team complete
I/p o/p QA team

test plans, test templates, test


Code - basic blocks of code- unit scenarios, test cases, test data,
of code that is complete in itself unit - is tested and bug free reviews and obtain sign off

test plans, test templates, test


units of code with in an The integrated code- becomes one scenarios, test cases, test data,
integration flow unit reviews and get sign offs

Test reports - defects/defect All the activities- test execution,


reports- eventually a tested bug reporting and defect management.-
The code/build free product QA team will also provide its sign off

Training the users, identify some


the code- the system tested critical test cases, support UAT users,
code UAT reports, UAT signed off project report UAT status

You might also like