Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open environment for testing and presenting #33

Open
tobijuon opened this issue Oct 21, 2021 · 5 comments
Open

Open environment for testing and presenting #33

tobijuon opened this issue Oct 21, 2021 · 5 comments
Assignees

Comments

@tobijuon
Copy link

Open testing environment

An open environment in the same state as the live version with open accessible accounts for tests from people not having any connection to a group (Abteilung). Could work similar to the testing environment of MiData: https://pfadi.swiss/de/apps/midata/#Testumgebung
Therefore, an examplary dataset would be essential.

Examplary dataset

An open dataset with randomized data unrelatet to the truth for one examplary group (Abteilung), to demonstrate the functions of the HealthCheck to the public without data privacy concerns.

@carlobeltrame
Copy link

Running a separate instance for testing which is freely available for testing would clearly be the best option for this. At this year's MiData Konferenz, one of the topics was also whether we should work on better dummy data for the testing environment of MiData, which would almost automatically benefit such a testing environment of HealthCheck.

However, since running and maintaining an instance of an application is expensive, an intermediate free solution would be to document how to run HealthCheck and an instance of MiData locally on one's own computer. Since both projects offer development setups based on docker-compose, only docker-compose and git are necessary to run these applications locally. I'd be happy to share my findings so far, and work on making this setup simpler in the future. The exemplary dataset could then be provided in the form of an SQL dump for the local MiData instance, or in the form of database seeds (i.e. randomly generated but useful data which is created when starting the local MiData instance). But to be fair, this kind of solution is not really suited for a general target audience, at least some technical background is probably still needed.

@tobijuon
Copy link
Author

Thank you for your remarks. As the MiData-PO already knows, we would be really interested in such "better dummy data".

We would be really interested in your findings to run and test locally anyway. What would be an appropriate way to do so? A PR for the README.md, a new sub-page or a new section on the PBS-page?

Is there way to fetch data from the MiData staging environment?

@carlobeltrame
Copy link

Yes, I would document my findings somewhere on GitHub. The PBS page seems less technical to me. Anyone who wonders about the inner workings of HealthCheck will need to come to GitHub anyways.

@carlobeltrame
Copy link

carlobeltrame commented Oct 26, 2021

In the same documentation, we could of course include instructions for running the local HealthCheck against the MiData staging environment, as well as instructions for running it against a local instance of MiData. These cases both work similarly.

@vouillamoz
Copy link
Member

@PapillonAudrey ist dieses Issue noch aktuell?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants