Medic conf actions tests

[ngaruko]

Description

Testing major medic conf actions
medic/medic-release-testing# 83

Code review checklist

• Readable: Concise, well named, follows the style guide, documented if necessary.
• Documented: Configuration and user documentation on cht-docs
• Tested: Unit and/or e2e where appropriate
• Internationalised: All user facing text
• Backwards compatible: Works with existing data and configuration or includes a migration. Any breaking changes documented in the release notes.

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[dianabarsan]

Nice work!
I added a couple of recommendation inline, but nothing major.

I think this is very useful to have here, thanks a lot for adding it.
Ideally we should also have something similar in medic-conf and run it against the current working branch of medic-conf.

[ngaruko]

Nice work!
I added a couple of recommendation inline, but nothing major.

I think this is very useful to have here, thanks a lot for adding it.
Ideally we should also have something similar in medic-conf and run it against the current working branch of medic-conf.

True. We need to find ways to run this in medic-conf. Not as easy as here as we need the required files and folders in medic-conf - and an instance to point to (or boot up cht-core in medic-conf)

To be discussed - how to include similar tests in medic-conf

[dianabarsan]

Nice work! I only have one pending request, that was skipped in the previous review.

Could you please rebase off of master to fix the conflicts. Thanks!

[dianabarsan]

Awesome work! It's great to have these tests!