-
Notifications
You must be signed in to change notification settings - Fork 7
Add suite creation and jedi config render tests #751
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
base: develop
Are you sure you want to change the base?
Changes from 41 commits
4f48070
d32c3b9
28be5ba
3d571cf
1e65b35
f69dbe5
7041a44
07714ea
07add94
d3abcca
b742b84
08e8674
e42e3b9
a97c229
51cecfe
5f332cd
2a5a0f8
987bbaf
9119709
4b1a98c
eb58146
912b3f0
7430617
9c342ca
13247a2
a0a9d28
4ccbc63
05f8a7d
1ff3b24
d5602da
8cc96f8
df0d9df
3e9a44f
3d9a7f2
b25a6dd
7a20636
cc4cd94
e6a8e05
9edbcff
96e9e20
5b7bed3
6ffd59b
63dac86
9a5b995
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,3 +17,11 @@ By default, swell will create several directories in the working directory that | |
| ```yaml | ||
| test_cache_location: /discover/nobackup/<user>/swell-test-cache | ||
| ``` | ||
|
|
||
| ## Code tests | ||
|
|
||
| ### Suite creation test | ||
| The suite creation test attempts to construct experiments for all suites within swell in a temporary directory. If one fails, try creating the suite on its own to make sure it is configured properly. Ensure all values are valid and are not filled by the templates `defer_to_model` or `defer_to_platform`. | ||
|
|
||
| ### JEDI Config test | ||
| The JEDI config test generates mock configs for jedi executables in a dry-run mode, where obs will not be checked and placeholders will be used for experiment filepaths. These configs are compared against reference files located in `src/swell/test/jedi_configs/`, and named `jedi_<suite>_config.yaml`. Any difference in values in these yamls will cause this test to fail, so ensure any differences created are intentional, then run `swell utility CreateMockConfigs` to automatically generate new reference files for all suites. These new files are placed in the `jedi_config` location in the source code. | ||
|
||
Uh oh!
There was an error while loading. Please reload this page.