4Sure Test Summary
Last updated
Last updated
Copyright © OpenG2P. This work is licensed under Creative Common Attribution (CC-BY-4.0) International license unless otherwise noted.
This document summarises the test strategy, deliverables, and results recorded while testing the 4Sure application.
The purpose of testing is to ensure the functionality of the features in the 4Sure application is in line with the requirements of the stakeholders.
The scope is to test the functionality of the features in the 4Sure application.
| Feature | Test Cases |
|---|---|
The 4Sure application is tested in standalone mode by installing the application on Android devices.
| Device Model | OS Version | Test Result |
|---|---|---|
The launching of 4Sure application via ODK collect is tested by installing the application on above mentioned Android devices, and
Used explore environment for ODK collect
The below test types are used to make sure that the application is tested properly.
For detailed summary, click the below link.
You can find the defect summaries that are identified during testing in the below links.
Build Date: 2024-03-21
Build name: 4Sure-debug-v0.7.0-21-03-2024-arm64-v8a.apk
Deployment Target: Android 12 and above
| Test type | Description |
|---|---|
| Environment | No. of test case executed | Passed | Failed | Not executed |
|---|---|---|---|---|
| Defect summary | Link |
|---|---|
Feature in scope
Feature not in scope
Samsung Galaxy Tablet
Android V14
Pass
Moto G(60)
Android V12
Pass
Google pixel 6a
Android V13
Pass
Sanity
It is used to ensure that the major functionality of the application is working fine.
Regression
It is used to ensure that the entire functionality of the application works fine.
4Sure application Standalone mode
43
36
3
4
Launch 4Sure application via ODK Collect
40
34
2
4
Total
83
70
5
8
Total number of defects found
Total number of defects in "To Do" states
Total number of defects in "Done" states