-
Notifications
You must be signed in to change notification settings - Fork 1
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
SP-1612 Add tests to ensure the Scheduler Snapshot Dashboard is working properly in LFA mode #111
base: main
Are you sure you want to change the base?
Conversation
ab18a70
to
8aff75b
Compare
The tests should pass once the LFA fix is merged |
2068119
to
37c1ba1
Compare
@ehneilsen Thanks for merging the fix into this PR. If you're happy with the changes, can you please approve it? |
I'd like to see the tests pass first, but am having trouble getting it to. The issue isn't with this code itself, I think, but rather that I need to find a version of |
I use the latest version of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just hoping to merge this PR soon to avoid leaving it for long time then struggling with rebasing and changing environment to be able to run it again.
Go ahead an rebase it now, and then merge. Yes, the LFA stuff will still be broken, but not more broken than it already is, or for a different reason, so I think merging is okay.
37c1ba1
to
3914c8d
Compare
Thanks Eric. One test is failing though. The dashboard also fails when trying to make the basis functions dataframe. It's the same error raised in the failing test
|
Yes, there was another late change in |
3914c8d
to
4a9e75c
Compare
This PR adds 2 tests for the LFA mode in addition to the playwright tests. One test basically makes sure the dashboard is rendering as expected, whether it's an LFA environment or not.
If it's an LFA environment, the other test checks that at least one snapshot is retrieved and that it is read successfully.
I used the environment variables needed for accessing the S3 buckets to check if it's a LFA environment or not.
The tests are async because the
efdclient
functions are async. Hence, thepytest-asyncio
dependency is added totest-requirements.txt
. A related config is added topyproject.yaml
as well.The async tests had to be moved to a separate file. Apparantly the way pytest runs async tests aren't compatible with how the sync unittest tests run. When added to the main file, the tests always pass, regardless of what happens in there.