Open-EO / Open-EO/openeo-python-client
integration tests for openeo-python-client
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Idea brought up by @pvbouwel while discussing https://github.com/Open-EO/openeo-python-client/pull/805 and https://github.com/Open-EO/openeo-python-client/pull/750:
Set up integration tests suite for aspects of python client where unit tests require so much tricky mocking that it becomes almost pointless.
possible features that are good candidates for integration tests:
- OIDC auth flows with (e.g. against dummy keycloak instance)
- multi job manager
- S3 asset management
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing pull requests #805 and #750, where the integration-test idea was discussed. Scope the proposed suite around OIDC authentication flows, the multi-job manager, and S3 asset management, then define which behavior should be exercised against real services such as a dummy Keycloak instance. Done means the client has a maintainable integration-test setup covering the selected candidates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100