... | ... | @@ -54,6 +54,8 @@ If there is no baseline csv file, the test suite will plot data from the generat |
|
|
|
|
|
<img src="uploads/2b401003ca76417a12c366f592106e1b/image.png" width="50%"/>
|
|
|
|
|
|
If you would like to run a specific subset of scenarios or tests, you can open any config file and copy out test lines and paste them into the DebugRun.config. See `Development Approach` below.
|
|
|
|
|
|
Next, let's dig into how this works and what all we can run.
|
|
|
|
|
|
Verification Test Configurations
|
... | ... | @@ -146,7 +148,6 @@ Running the full test suite, and even the ScenarioVerification.config can take q |
|
|
|
|
|
Once we are happy with how our model updates are performing with these scenarios, we can run the full suite of tests to see how this update affects all other scenarios, via `run SceanrioVerfication`
|
|
|
|
|
|
|
|
|
Validation
|
|
|
----------
|
|
|
|
... | ... | @@ -154,4 +155,4 @@ Validation |
|
|
Rebasing
|
|
|
--------
|
|
|
|
|
|
[How to rebase the verification baselines](https://gitlab.kitware.com/physiology/engine/wikis/Updating%20Baselines) |
|
|
Once you have made changes to Pulse and have fully investigated and any failing test cases are still producing valid results, you will need to rebase the verification baseline csv files](https://gitlab.kitware.com/physiology/engine/wikis/Updating%20Baselines). This needs to be done via a Pulse maintaining member. |
|
|
\ No newline at end of file |