Test Summary Report

Table of Contents

1. Purpose...................................................................................................................................................2
2. Application Overview..............................................................................................................................2
3. Testing Scope..........................................................................................................................................2
a) In Scope.......................................................................................................................................2
b) Out of Scope.................................................................................................................................2
c) Items not tested..........................................................................................................................2
4. Automation Testing Status......................................................................................................................3
a) Automation overall report...........................................................................................................3
5. Metrics....................................................................................................................................................4
a) No. of test cases planned vs executed & No. of test cases passed/failed.......................................4
b) No of defects identified and their Priority & Severity......................................................................4
c) Defects distribution – module wise.................................................................................................6
6. Types of testing performed.....................................................................................................................6
a) Automation Testing of Five modules...............................................................................................6
b) End to End Manual Testing of Five modules....................................................................................6
c) Security Testing of Five modules.....................................................................................................7
7. Test Environment & Tools.......................................................................................................................7
8. Best Practices..........................................................................................................................................7
9. Exit Criteria..............................................................................................................................................7
10. Conclusion/Sign Off...............................................................................................................................7

Test Summary Report

1. Purpose

This document explains the various activities performed as part of Testing of ‘Techgig’
web-application.

2. Application Overview
‘TechGig’ is India’s one of the largest technology community which allows users to interact with
their community members. It is also a great platform to showcase your talent and “though
leadership” through various means like webinars and coding contests. It has just over 500000
members in India; mostly within application development/testing technologies like Java, php,
android, testing and many more.

3. Testing Scope

a) In Scope
Functional Testing for the following modules are in Scope of Testing
 Login/Signup
 Contest Participation
 Skill test Participation
 Attending a webinar
 Applying a job

b) Out of Scope
Performance & Load Testing was not done for this application.

c) Items not tested

Apart from the above mentioned five module rest of the other modules in the website
are not tested.

Test Summary Report

4. Automation Testing Status

a) Automation overall report

Test Summary Report

5. Metrics
a) No. of test cases planned vs executed & No. of test cases passed/failed

TCs TCs
Test cases planned Test cases executed
Passed Failed
107 107 105 2

2%

TCs Pass
TCs Failed

98%

b) No of defects identified and their Priority & Severity

Priority levels Bug Count

P1 – Show Stopper 2
P2 – High Attention 15
P3 – Medium priority 9
P4 – Low priority 12

Test Summary Report

 15

12

BUG COUNT

Severity levels Bug Count

S1 – Critical
severity 10
S2 – Major severity 3
S3 – Normal
severity 11
S4 – Minor severity 14

S4 – Minor severity

S3 – Normal severity

S2 – Major severity

S1 – Critical severity

0 5 10 15

Test Summary Report

c) Defects distribution – module wise

Module Name Bug Count

Practice 7
Skill tests 9
Code challenges 8

Webinars 4
Tech news 4
Security Testing 6
38

Practice Skill tests

16% 18% Code challenges Webinars
Tech news
11% Security Testing

10% 24%

21%

6. Types of testing performed

a) Automation Testing of Five modules
• We have done the testing for based on the end to end
functionalities of the web application.

b) End to End Manual Testing of Five modules

• We have done the testing for based on the end to end
functionalities of the web application.

Test Summary Report

 c) Security Testing of Five modules
• We have done the testing for based on the end to end
functionalities of the web application.

7. Test Environment & Tools

Application URL https://www.techgi

g.com
Automation Testing Selenium
webdriver 3.9.1
NUnit : 3.9.0
Security Testing Jsky (v3.5.1.905)
windows installer

8. Best Practices
• Smoke test cases were automated and the scripts were run, which ran fast and
saved time.
• Automation scripts were prepared to do end to end testing .do end to end
testing. Business critical scenarios are separately tested on the entire
application which are vital to certify they works fine.

9. Exit Criteria
a) All test cases should be executed – Yes
b) All defects in Critical, Major, Medium severity should be logged– Yes.

10. Conclusion/Sign Off

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

Test Summary Report