Contributions & Payments Modules Test plan
This page summarizes the openIMIS features that were determined in the analysis and therefore tested for delivery for the Contributions and Payment modules.
The module features are, among others, used within the scope of Beneficiary Enrollment business processes. However the testing is determined for the use of the module at hand, and not interactions between different modules. An overall cross-sectional testing will need to be done at the end of the migration process.
This Test plan will be completed by specific use cases according to the needs arising.
Contributions module
Pre conditions | Actions | Expected results |
| 1.1 Search by Payer | A dropdown menu should appear with the list of payers by clicking on the arrow on the right of the selector. The user should therefore be able to select contributions related to a specific payer |
1.2 Search by Payment Type | A dropdown menu should appear with the list of types by clicking on the arrow on the right of the selector, to select contributions related to a specific payment type | |
1.3 Search by Payment date to | The user should be able to type in a date or use the date selector button to enter the “payment date to” to search for contributions with a payment date equal or earlier than the specified date | |
1.4 Search by Date | By clicking on the date selector button, a calendar selector should pop up. By default the calendar should show the current month, or the month of the currently selected date, with the current day highlighted. At any time during the use of the pop-up, the user should see the date of today.
| |
1.5 Search by Contribution category | A dropdown menu should appear to select the contribution category that matches with the type of contribution paid; by default “contributions and others” and “photo fee” should display | |
1.6 Search by Contribution paid | The user should be able to type in the contribution paid to search for contributions with the paid amount, greater or equal to the typed amount | |
1.7 Search by Region | A dropdown menu should appear with the list of regions. The user can select one of them. The list should display only the regions assigned to the current logged in user. If there is only one region, then it should be automatically selected | |
1.8 Search by District | A dropdown menu should appear with the list of districts. The user can select one of them. The list should display only the districts assigned to the current logged in user. If there is only one district, then it should be automatically selected | |
1.9 Display the Historical records | The user should be able to click on “historical” to see the historical records matching the selected criteria. They should be displayed with a strikethrough to differentiate them rest others | |
1.10 Filter the records | The user should be able to use the search button to filter the records, and the results should then appear in the result panel | |
1.11 Display the results | The result panel should display a list of all contributions found, matching the selected criteria in the search panel. In the legacy version, the selected record is highlighted with light blue, while hovering over records changes the highlight to yellow. The new module version should have a similar feature, following the new module branding guidelines | |
1.12 Select a record | In the legacy version, the leftmost record contains a hyperlink which if clicked, re-directs the user to the actual record for detailed viewing if it is a historical record or editing if it is the current record. In the new module, an update should be included: selecting a specific contribution should lead the user to contribution details. A direct link to family (as exists already in other table) should be added | |
1.13 Click on the cancel button | The user is redirected to the homepage | |
1.14 Enter data in the Payer field (if the contribution is not paid by the family/group itself) | The user should be able to select from the dropdown menu from a list of available payers | |
1.15 Enter data in the Payer field (if the contribution is paid by the family/group itself) | The payer field appears blank | |
1.16 Enter data in the Contribution paid field | This field should be mandatory and the user should be able to enter the receipt identification for the contribution. The receipt identification has to be unique within all policies of the insurance product | |
1.17 Enter data in the Receipt n° field | This field should be mandatory and the user should be able to enter the receipt identification for the contribution. The receipt identification has to be unique within all policies of the insurance product | |
1.18 Enter data in the Payment date field | This field should be mandatory and the user should be able to enter the date of payment for the contribution. The user should also be able to use the button next to the date of payment field to select a date to be entered | |
1.19 Enter date in the Payment type field | This field should be mandatory. The user should be able to select from a dropdown menu the available types of payment the payment type for the contribution | |
1.20 Save the entered data | Only once all mandatory fields are entered, the user should be able to click on the “save” button and this should save the record. Depending on the contribution paid, the following messages should appear:
The user should be redirected to the Family Overview Page with the newly saved record displayed and selected in the result panel and a message confirming the contribution has been saved on the information panel should be displayed If mandatory data is not entered at the time the user clicks the “save” button, a message should appear in the information panel, and the data field should take the focus (asterisk) | |
1.21 Cancel the data entry process | The user should be redirected to the family overview page | |
1.22 Select the “Green plus sign” to add a contribution | The user should be redirected to the contribution page with all data fields empty | |
1.23 Select the “Yellow pencil sign” to edit a contribution | The user should be redirected to the contribution page with the current information loaded in the data entry fields | |
1.24 Select the “Red cross” sign | The user should see te currently selected record disappear. Before deleting, a confirmation popup should be displayed, requiring the user to confirm if the action should be carried out: “Are you sure you want to delete the premium?” When a contribution is deleted, all records pertaining to the deleted contribution should still be available by selecting historical records (see 1.9 for testing) |
Payments module
| 2.1 Search a Payment based on the Date | By clicking on the date selector button, a calendar selector should pop up. By default the calendar should show the current month, or the month of the currently selected date, with the current day highlighted. At any time during the use of the pop-up, the user should see the date of today.
|
2.2 Search a Payment based on the Member | The user should be able to select from a dropdown menu the members associated with the payments available | |
2.3 Search a Payment based on the Policy | The user should be able to select from a dropdown menu the policies associated with the payments available | |
2.4 Filter the records | The user should be able to use the search button to filter the records, and the results should then appear in the result panel | |
2.5 Select the “Yellow pencil sign” to edit a Payment | The user should be redirected to the payment page with the current information loaded in the data entry fields. The user should be able to link the payment to a specific contribution as part of the “edit” part or as a separated action “match to contribution” | |
2.6 Select the “Green plus sign” to add a contribution | The user should be redirected to the payment page with all data fields empty | |
2.7 Check if the payment is received | Once payment(s) is (are) received and cover the expected contribution(s) amount (and the policy value), the user should see the policy status change and become either:
| |
2.8 Manually match a payment to a contribution | The user should have a functionality allowing to match a payment to a contribution |
Did you encounter a problem or do you have a suggestion?
Please contact our Service Desk
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/