EUMS Acceptance Report

1. Introduction

1.1 Purpose of the document

This EUMS Acceptance Report provides a summary of the results of test performed as outlined within this document.

1.2 Application Overview

EUMS is a web based resource tracking and monitoring application. Resources imported can be delivered (or distributed) to other partners. During the process, users (UNICEF_admin and Implementing Partner) can assign receivers’ information and collect feedback from receivers using the application. Users can also check the reports about delivery, item and stock, to make sure all resources are delivered to end_users.

2. Test Scope

2.1 In Scope

Functions for the following modules are in scope of test:

1. User (include: RapidPro sending message to user)
2. Contact (include: pushing all contacts to RapidPro)
3. Consignee
4. Delivery
5. Distribution
6. Reports
7. Alerts
8. Dashboard
9. System Settings (include: vision import)

Performance Testing was done to test the time needed when loading a page. The average speed for loading dashboard page on test server is around 0.7s, and it would take 1s more to finish the map and etc components.

3. Test Summary

3.1 Code Level

1. Unit Test

Unit test aims to verify the result of a particular function or method of a class instance. We use test to drive development, called TDD. Unit test was done before developing a new function or method, to ensure the code logic is right.

2. Integration Test

Integration tests verify that the components of application work together. In this case, the interaction between two or more “units” is explicitly tested.

3. Functional Test

This test is performed to verify that the application performs and functions correctly according to requirements. Functional tests are user facing, they are written by developers together with BA(Business Analyst) and QA(Quality Analyst), from end user’s perspective. New functional tests were added when a feature finished.

Note: Test coverage is tracked through third-party tool "coveralls".

3.2 Business Level

1. Smoke Testing

This test was done whenever a Build received (deployed to Test environment) for testing to make sure the major functionality are working fine, Build can be accepted and test can start.

2. System Integration Testing

This is the test performed on the application under test, to verify the entire application works as perfect as the requirements. Critical Business scenarios were tested to make sure important functionality in the application works as intended without any errors.

3. Regression Testing

Regression Testing was performed each time a new build is deployed for testing which contains defect fixes and new enhancements, if any. Regression Testing is being done on the entire application and not just the functionality and defect fixes. This test ensures that existing functionality works fine after defect fix and new enhancements are added to the existing application. Test cases for new functionality are added to the existing test cases and executed.

3. Test Results

In EUMS, all tests are completely executed and passed. We have reasons to believe that, at present, the application has no obvious and fatal errors.

Appendix

1. End Use Monitoring System Version 2.0 User Guide for System Admin
2. End Use Monitoring System Version 2.0 User Guide for Implementing Partner