Skip to content
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

connection reuse in workflow tests #38

Open
soxofaan opened this issue Jan 23, 2024 · 0 comments
Open

connection reuse in workflow tests #38

soxofaan opened this issue Jan 23, 2024 · 0 comments

Comments

@soxofaan
Copy link
Member

soxofaan commented Jan 23, 2024

While working on #37 I noticed that there is almost a full openeo.connect + auth + capabilities discovery cycle for each workflow test, which is quite time consuming, especially if you are using process/level filtering features to skip certain tests.

Reason is that most workflow tests are isolated in their own module and the connection fixture has "module" scope, meaning that a new connection is created (auth+capability discovery included) for each module.

@clausmichele I think we should consider grouping workflow tests more, e.g. per level or something.

Note: this is just a "nice to have" task, I don't think this some kind of blocker for closure of the current project. I just wanted to park that idea here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant