Testing –

1. Test Strategy :
Go to start of metadata
Objective:

It is intended to simulate the real business user scenarios and validate the system under test and
its components for integration and data integrity.

It is performed from start to finish under real-word scenarios like communication of the
application with other applications like Mobile App, ESBG, Toshiba POS, Digital API/interface, EPS,
Stratus, Loyalty, 3rd party/vendor systems etc., hardware, network and database in a controlled
end-end test environment with actual production like data.

Scope:

Introduction

Defect severity is very important in terms of deciding impact on the system on functionality

execution failure.
Defect Definition
Severity

Severity 1  Critical component of the system is not functional or data integrity

issue exists with no work around
 Defect causes the system/application to halt or crash or loss of data
or security breach or be inoperable
 Basic functionality is not accessible from any navigational point
 Substantial performance degradation is experienced

Severity 2  A major system/component is unusable due to failure or incorrect

functionality but can have some work around/alternative way of
achieving the functionality
 It can cause serious problems such as lack of functionality or
insufficient or unclear error messages that can have major impact to
the user
 Prevents other areas of system/application from being tested
 Significant amount of data misrepresentation
 Serious defects that do not crash the system or corrupt the data but
prevent the user from continuing in that specific functional area 

Severity 3  Defect that is not impending progress but requires attention if the
test/business scenario is to pass the testing stage
 It impacts moderate on testing
 In correct functionality of system/component or process
 There is a simple work around

Severity 4   Cosmetic issue that do not affect usability such as spelling,

grammar etc.
 Defect Definition
Severity

 UI/navigational disparity b/w actual functionality and functional

specification such as wireframes or style guides that do not affect
system operation
 Occurrence of the problem is low or does not impact  testing
progress

Test Reporting/Metrics:
Metric Description

End-end test scenarios/cases Test design progress

design progress

End-end test Test Execution progress

scenarios/cases execution
progress

Defects Discovered Total defects discovered during end-end test cycle

Open Defects All Priorities Trending of all the open defects priority wise

Open Defects All Severities Trending of all the open defects severity wise

Defects Aging  Displays how long(Hours/Days/Weeks) a particular

defect took to get closed for good in the Jira tool 

 Open Defects-Critical/High Trending of open defects- Critical/High priority only 

 Open Defects-Severity 1/2 Trending of open defects- Severity 1/2 only