-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add developer instructions #49
Comments
Here's an example of the errors I get when trying to run the tests:
|
This is an excellent suggestion. I should be done with a PR addressing this shortly :) |
Hmmm a bunch of tests are failing because AEMO has changed how the bidding data is stored again. You can take a look at #50 in the interim, but I'll complete the guide on testing once I get them all running again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I want to write a pull request for #47 . I'm not sure exactly how to get set up and run tests.
For #48 I just did
pip install -e ./
in a virtual env, then ran a test script outside the repo. But for #47 I'll need to be more comprehensive with tests.I can see from the existing test scripts that this project uses
unittest
notpytest
. But I can't figure out how to run them. (python3 -m unittest
says no tests found.) Should I even be running all tests? (Seeing #16 makes me think the tests aren't supposed to be run for each change. How can I run just the relevant subset?)I see a
pyproject.toml
. I don't know how to use that. That file mentions rye and hatch. Do I need those?I see
requirements*.lock
files, instead ofrequirements.txt
. I don't know if pip will find them, or if I'm supposed to use poetry or something else.I would like a paragraph added to the README or Wiki that explains how to get set up, run tests etc.
The text was updated successfully, but these errors were encountered: