2018-11-06 Reporting Test Plan Meeting notes

Owned by Sam Im (Deactivated)
Last updated: Nov 12, 2018 by Clay Crosby (Unlicensed)
2 min read

Date

Nov 6, 2018

Attendees

  • @Sam Im (Deactivated)

  • @Joanna Szymańska (Deactivated)

  • @Joanna Bebak (Deactivated)

  • @Clay Crosby (Unlicensed)

  • @Craig Appl (Unlicensed)

  • @Wesley Brown

Goals

  • The purpose of this meeting is to understand the test plan for reporting that was created by Team Ona, and what will need to be done for the 3.5 release.

    • Who owns the testing and the test plan?

    • How are existing reports impacted? Should they be tested?

    • Are any additional resources needed? Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

Testing Reports such as Timeliness reports, stock out reports

Three tables that contain data, and there are 20 charts based off this data. Half day to test reporting end to end.

https://reporting-gap-data.openlmis.org (test with Admin user)

 



  • Accuracy: queries spin off a table, and then Superset builds charts

  • Spotchecking data between Malawi tables and what appears in the charts

  • We could make manual test cases for validation by manually creating the demo data

  • Adjustment summary report: clear data validation without computations so this is an easy report to check.

  • Timeliness report we will need to be careful with because the calculations use dates. Dates will need to be manipulated

  • We need a requisition workflow to test the end to end creation of a requisition to reporting.

  • Will UAT be updated to complete this testing? We need logins to test reporting as well. Use Malawi server?

    • Clay suggests: Enter test data into the server with Malawi data, which users to use for testing (admin)

  • Clay can write test cases for the report validation









Action items

@Clay Crosby (Unlicensed) to determine who will be the backup from Team Ona for questions about reporting during RC testing.
@Clay Crosby (Unlicensed) to write test cases for the report validation and notify @Sam Im (Deactivated) to review during Sprint 112
@Sam Im (Deactivated) to complete requisition workflow end to end in the test environment provided by Clay in Sprint 112
@Sam Im (Deactivated) to add test cases to test plan & RC queries for creating test cycles

Decisions

  1. Previous reports should not be fixed - Superset reports are the replacements and should be validated and fixed if needed. We do not see a benefit in the validating of old reports.

  2. Reporting test cases will be included in 3.5 RC test plan and included as part of this testing.

OpenLMIS: the global initiative for powerful LMIS software