Scribd
Upload
16 views

Sample Testing Report For Testing Course

The test summary report summarizes testing activities for the previous Android build of the XYZ Mobile application from March 18-22, 2023. It shows that 70 test cases were run with 40 passing and 18 failing, up from the previous build. 47 defects were found, more than the previous 33 defects due to new features, though quality increased. Suggestions include using a defect tracking tool like JIRA to more efficiently manage defects.

Uploaded by

claudison.ubers
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
16 views

Sample Testing Report For Testing Course

The test summary report summarizes testing activities for the previous Android build of the XYZ Mobile application from March 18-22, 2023. It shows that 70 test cases were run with 40 passing and 18 failing, up from the previous build. 47 defects were found, more than the previous 33 defects due to new features, though quality increased. Suggestions include using a defect tracking tool like JIRA to more efficiently manage defects.

Uploaded by

claudison.ubers
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Test Progress Report

For XYZ Mobile App[Android Version]

Version Date Created By

Version 2.1 22/03/2023 Tarek Roshdy


Report Outline:

Introduction

Test Case Execution Status

Bug Reports status

Testing suggestions for next period

PAGE 1
Introduction

This Test summary report is used to clarify the testing activities that happened for the previous Android build
of the XYZ Mobile application in the period from (18-3-2023) to (22-3-2023).
The goal of this report is to show the following:
● Status of test cases executed
● Defects found & their status
● Suggestions for next period of testing

PAGE 2
Test Case Execution Status

This is the status of all the test cases that are run on the Android version:

Test Case Status Current Build Results Previous Build results

Total Number of TCs 70 (⇑) 63

Passed TCs 40(⇑) 31

Failed TCs 18(⇑) 16

Blocked/Skipped TCs 12(⇓) 16

This is the status of all the test cases that are run on the iOS version [There is no iOS build]:

Test Case Status Number of Test Cases

Total Number of TCs NA

Passed TCs NA

Failed TCs NA

Blocked/Skipped TCs NA

● Test Case Execution notes:


○ The number of passed test cases increased from 31 to 40, which indicates an increase in the
quality of the application
○ The number of failed & blocked/skipped test cases decreased from 32 to 20 which also indicates
an increase in the quality of the application
○ Note that all test cases that included integrations between two users were executed on two
android devices because there is no iOS build now. Testing integrations using iOS might cause
more test cases to fail

PAGE 3
Defects Status for Android

This table lists the number of defects in the Android version based on their priority:

Defect Status Current Build Defects Previous Build Defects

Total Number 47(⇑) 33

High 23 (⇑) 12

Medium 13 (⇑) 10

Low 8 (⇓) 11

This table lists the number of defects in the Android version based on their type:

Defect Status Current Build Defects Previous Build Defects

Total Number 47(⇑) 33

Functional 22 (⇑) 20

UI/UX 23 (⇑) 10

Performance 2 (⇓) 3

● Android Defects notes:


○ The number of defects in the new build is more than the number of defects in the previous build,
but although, we consider that the quality has increased. The cause of the high number of defects
might be that new functionalities are added in the new build.

PAGE 4
Testing suggestions for next period

● We suggest that a defect tracking tool like (JIRA) is used in writing defects so that the defect is tracked
from reporting to resolving. This will reduce the time required to write new defect reports for each build.

PAGE 5

You might also like