-
Notifications
You must be signed in to change notification settings - Fork 13
EUMS Acceptance Report
This EUMS Acceptance Report provides a summary of the results of test performed as outlined within this document.
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.
Functions for the following modules are in scope of test:
- User (include: RapidPro sending message to user)
- Contact (include: pushing all contacts to RapidPro)
- Consignee
- Delivery
- Distribution
- Reports
- Alerts
- Dashboard
- 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.
1.Unit Test
To ensure the correctness of code logic during front-end development, Unit Test is used to cover functions for each story as many as possible. The popular combination of Karma and Jasmine is applied, Karma provides a reliable test environment for actually running tests and displaying execution results while Jasmine is a behavior-driven development framework for writing well-structured tests.
2.Backend Test
To ensure the correctness of code logic during back-end development, backend test is implemented to cover as many data processing and business computation as possible. For EUMS, backend tests are writing by using test modules provided by Django and its extended REST frameworks, which is inherited from Python standard library.
3.Functional Test
To ensure the health of core features of EUMS and reduce manually repetitive test, Functional Test is performed by using Protractor. Protractor is an end to end test runner which simulates user interactions by running in a number of real browsers, such as Chrome, Firefox, Safari etc.
1.Smoke Testing
Smoke Testing is carried out 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
System Integration Testing is performed on the application under test, to verify the entire application works in the light of requirements. Critical Business scenarios are tested to make sure important functionality in the application works as intended without any errors.
3.Regression Testing
Regression Testing is 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.
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.