Scribd
Upload
49 views

Final Test Report Signal App

The document provides a test summary report for the Signal mobile application. It covers the testing scope, metrics including number of test cases executed and defects found. The types of testing performed are described such as functional, interrupt, usability, memory leakage and performance testing. The test environment and tools used are also mentioned. The report concludes with lessons learned, recommendations, best practices and exit criteria being met for the application to go live.

Uploaded by

Kalpesh Mehta
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
49 views

Final Test Report Signal App

The document provides a test summary report for the Signal mobile application. It covers the testing scope, metrics including number of test cases executed and defects found. The types of testing performed are described such as functional, interrupt, usability, memory leakage and performance testing. The test environment and tools used are also mentioned. The report concludes with lessons learned, recommendations, best practices and exit criteria being met for the application to go live.

Uploaded by

Kalpesh Mehta
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Test Summary Report - Signal Mobile Application

Contents
1. Purpose.....................................................................................................................................2
2. Application Overview...............................................................................................................2
3. Testing Scope............................................................................................................................2
4. Metrics......................................................................................................................................3
5. Types of testing performed......................................................................................................6
6. Test Environment & Tools........................................................................................................6
7. Lessons Learnt..........................................................................................................................7
8. Recommendations....................................................................................................................7
9. Best Practices...........................................................................................................................7
10. Exit Criteria...............................................................................................................................8
11. Conclusion/Sign Off..................................................................................................................8
12. Definitions, Acronyms, and Abbreviations...............................................................................8

STAD Solution Test Summary


Report
1. Purpose

Signal can use on Apple and Android smart phones and via desktop. User need is a
phone number to join Signal App. You can text or make voice or video calls with friends,
either one-on-one or in groups, and use Emojis reactions or stickers just like in other
apps

2. Application Overview

Signal is a free, privacy-focused messaging and voice talk app, Signal gives you


encrypted messages, as well as voice and video calls. It relies on data, so it's a great
option for free calls and texts over Wi-Fi. This can be a huge advantage for those of us
who don't want to pay for SMS text messages and phone calls, or who want to make
free international calls

3. Testing Scope:
I. In Scope
Functional Testing for the following modules are in Scope of Testing
 Sign Up
 Chats
 New Group
 Account
 Settings
 Profile
 Legacy Group
 MMS Group
 Notification
 Privacy
 Data Usage

II. Out of Scope :


 Help
 Invite Friends
 Donate to Signal
 Linked device

III. Items not Tested :


Payment Gateway of third party system “Donate To Signal” Module cannot
tested.
4. Metrics :
d) No. of test cases planned vs executed
e) No. of test cases passed/failed

Test cases Test cases TCs TCs


planned Executed Pass Failed
50 47 47 3

Test Cases Pass Vs Fail

6%

1st Test Cases Pass


2nd Test Cases Failed

94%

f) No of defects identified and their Status &Severity

Critical Major Medium Cosmetic Total


Closed 0 0 0 0 0
Open 0 1 1 1 3
3
1 Defect Severity & Status

2
1.8
1.6
1.4
1.2
Open
1
Closed
0.8
0.6
0.4
0.2
0
Critical Major Medium Cosmetic

g) Defects Distribution – Module wise

Signup Chat New Account Settings Total


Group
Critical 0 0 0 0 0 0
Major 2 0 0 0 0 2
Medium 0 0 0 0 0 0
Cosmetic 0 0 0 1 0 1
Total--> 2 0 0 1 0 03
Defects Distribution-Module Wise
10%

40%

Sign Up
30% Chats
New Group
Account
Settings

10% 10%
5. Types of testing performed:

I. Functional Testing :
This testing was done to check the functionality of all modules of application.

II. Interrupt Testing :


This testing was done to check if any interruption like SMS, call, notification etc
and this interruption didn’t down the performance of the application.

III. Usability Testing :


This testing was done to check that application is easily accessible to user and
it is user friendly or not and understand by the end user and convenient to
use.

IV. Memory Leakage Testing :


This testing was done to check Memory, if the Application has memory
consumption issue.

V. Performance Testing :
This testing was done to check the product that how it works in terms of
performance.

VI. Installation Testing :


This testing was done to check that application is easily installed or
uninstalled in every environment and if user uninstalled the app then all data
should be removed or erase from the system.

6. Test Environment &Tools :

Application https://signal.org/
URL
Apps Server
Database Oracle 12g
HP QC/ALM
7. Lessons Learnt:

S. No Issues faced Solutions

8. Recommendations:

 Admin control for defect management tool can be given to Offshore


Test lead/manager for providing access to Testing team.
 Each time the onsite Admin need not be contacted for requests whenever they
arise, thereby saving time due to the geographical time zone difference.

9. Best Practices:

 Smoke test cases were automated and the scripts were run, which ran fast
and saved time.
 Automation scripts were prepared to create new customers, where lot
of records need to be created for Testing.
 Businesscriticalscenariosareseparatelytestedontheentireapplicationwhich are
vital to certify they works fine.
10. Exit Criteria

I. All test cases should be executed –Yes


II. All defects in Critical, Major, Medium severity should be verified
and closed –Yes.
III. Any open defects in trivial severity – Action plan prepared with expected
dates of closure.

11. Conclusion/Sign Off:


As the Exit criteria was met and satisfied as mentioned in Section 10, this
application is suggested to ‘Go Live’ by the Testing team. Appropriate
User/Business acceptance testing should be performed before ‘Go Live’.

12. Definitions, Acronyms, and Abbreviations:


SMS - Short Message Service

MMS - Multimedia Messaging Service

**********

You might also like