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

Write test plan of things that need to be tested for 1.0 release #1373

Open
JoerivanEngelen opened this issue Jan 8, 2025 · 0 comments
Open
Assignees
Milestone

Comments

@JoerivanEngelen
Copy link
Contributor

JoerivanEngelen commented Jan 8, 2025

@deltamarnix mentioned that it is good to first write up what we want to test additionally to the stuff currently in our CI. We can then work on automating these if possible.

Test cases I'm currently thinking of:

Broad metrics we could test for:

  • Did the test run without error, did the validation succeed? 
  • Are the model input files written by iMOD Python the same (account for differences in sorting of List-based input)?
  • Are iMOD Python's run times in a similar ballpark?
  • Are there large differences in memory usage? Did memory usage explode?
  • How much does model output differ? (Compute some basic statistics, mean, min, max difference)
  • Make some plots of model output differences, these can help identifying differences.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📯 New
Development

No branches or pull requests

2 participants