-
Notifications
You must be signed in to change notification settings - Fork 3
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
Beginning of acceptance test framework #12
Conversation
8857edd
to
9984392
Compare
The tests are failing because Scheduler imports typing.Self, which was implemented in Python 3.11. The import is not from my code, it is from main. Should we stop testing python 3.10? |
|
@andnp we need your advice here. The Github workflow tests for this PR are failing because of two issues
I can fix both of these issues by editing |
This test includes some janky passing of results path. Needs to be fixed outside of test. Towards: #8
This makes pytest compatible with _utils.path.get_experiment_name() Fixes: #18
Yup, I think editing the workflow spec to solve both of these is a great strategy! I'm quite comfortable dropping 3.10 support |
Below tests are those on the main branch, the PR has an updated test.yaml and those pass when run locally through https://github.com/nektos/act. This fixes #20. |
This is the start of an acceptance test using mountaincar and softmaxAC. So far I have done:
tests/acceptance/softmaxAC_mc.py
with a test that writes to a database usingDefinitionPart
and reads from it usingExperimentDefinition
.tests/test_generate_configurations.py
, which tests the function inDefinitionPart.py
.