Test Report

Seite 1

Test report for applock:

Table of content:

Purpose of document

Application overview

Test summary

Test scope

In scope

Out scope

Not to be tested

Testing metrics:

Number of test cases planned vs executed.

Number of test cases passed vs failed.

Number of defects identified, status and severity.

Defect distribution.

Types of testing performed

Testing environment and tools

Lessons learned and strengths

Recommandations

Best practice

Exit criteria

Conclusion/ Sign off criteria

Purpose of document:

This document consists of test report for the AppLock application.

It explores what tests we have done on the application, the result of testing, how many bug it contains etc.

Application overview:

It is mobile application. It is used to lock the mobile applications for the privacy purpose. It provide feature of privacy album and video, privacy files etc. It also provide some other features like screen-lock, charging protection etc.

Test summary:

Start date

02-01-2017

End date

10-01-2017

Defect reporting tools

Jira

Number of bugs reported

5

Testing scope:

In scope tests:

Functional testing for the following modules:

Verification for password

Checked for verification for locking.

Done with the verification for themes tab.

Verified the menu tab.

Out scope tests:

Not done the load testing for this application.

Not to be tested:

Verification for privacy album.

Verify the privacy file.

Testing metrics:

Number of test case planned vs executed:

Test cases planned

50

Executed test cases

20

Non-executed test cases

30

Number of test cases passed vs failed:

Number of test cases executed

14

Number of test cases passed

9

Number of test cases failed

5

Number of defects identified their status and severity:

Defect identified

Status

Priority

Severity

On entering wrong password it still allows to enter into the application.

Failed

Highest

Hgh

On unlocking the app from the locked list, it is still locked.

Retest

Middle

Low

On selecting for the pattern type for the locking function, it still shows previous type of locking.

Retest

Middle

Low

Even if enter the password wrongly more than x times, it is not capturing the photo.

Failed

Middle

Low

Though we activate the vibrate on click the password, it will not vibrate on clicking right password

Failed

Low

Low

Defect distribution:

Verification for password.

Number of test case planned vs executed.

Number of test cases created

2

Number of test cases executed

2

Number of test cases not executed

0

Number of test cases passed vs failed.

Number of test cases executed

2

Number of test cases passed

1

Number of test cases failed

1

Checked for verification for locking.

Number of test case planned vs executed.

Number of test cases created

3

Number of test cases executed

3

Number of test cases not executed

0

Number of test cases passed vs failed.

Number of test cases executed

3

Number of test cases passed

2

Number of test cases failed

1

Done with the verification for themes tab.

Number of test case planned vs executed.

Number of test cases created

4

Number of test cases executed

4

Number of test cases not executed

0

Number of test cases passed vs failed.

Number of test cases executed

4

Number of test cases passed

3

Number of test cases failed

1

Verified menu tab.

Number of test case planned vs executed.

Number of test cases created

5

Number of test cases executed

5

Number of test cases not executed

0

Number of test cases passed vs failed.

Number of test cases executed

5

Number of test cases passed

4

Number of test cases failed

1

6. Types of testing performed:

Functional testing to test the various functions like verify password, verify locking and verification for screen lock etc.

GUI testing for testing how much user friendly it is.

7. Test environment and tools:

Testing environment: Lenovo A-6000, Kitkat version.

Testing tools: Testrail test case management tool, Jira bug tracking tool

8. Lessons learned and strengths:

9. Recommendations:

Should make module of security for more documents.

10. Best practice:

Add some more module for the security of the document.

11. Exit criteria:

Should complete all the test cases for the all module in scope.

Should pass all the test cases.

12. Conclusion/ Sign off criteria:

All the exit criteria are met and meet all the aspects of the client.