Open eric-jahn opened 5 years ago
I think #1 would just be a matter of comparing each cell, and if one of them does not match, list it and return "test fails".
For #2, we should first come up with a minimal list of validation checks.
Then we should write up the unit tests in psuedocode/JUnit/JMeter/whichever you guys agree on, and add to the build process, making HSLynk builds fail if this doesn't pass.
@kiadso Do you think you could work on #2? I think we could also use this sort of assistance for the LSA report validations as well, which you've worked on before.
Sure- just in a text file for now? Or markdown?
@kiadso Whichever you think is more useful. Markdown would be good I think, because we can make a nice wiki page out of it, and link it to the issue.
I agree- is there already an existing list for the previous APR?
@logicsandeep: Do you have a list of validations for the APR, or do we not have any tests yet? I guess we could start with the Sage validations, if HUD posted them.
The HMIS Glossary has a lot of validations in it too- I can just use that and the APR specs for now.
We should have APR unit tests that run on build, which compare:
1) ...to the HMIS APR sample CSV test kit report from HUD. Using the HUD HMIS sample test kit client data CSV, does the HSLynk APR return the same aggregate results as the HUD HMIS APR sample test kit report?
2) ...specific subtotals to grand totals. So these would be a series of report internal checks, like "with income + without income = total")?