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

Crosswalk And Document eoAPI Tests #88

Open
3 tasks
Tracked by #97 ...
ranchodeluxe opened this issue Jun 18, 2024 · 2 comments
Open
3 tasks
Tracked by #97 ...

Crosswalk And Document eoAPI Tests #88

ranchodeluxe opened this issue Jun 18, 2024 · 2 comments
Assignees

Comments

@ranchodeluxe
Copy link
Contributor

ranchodeluxe commented Jun 18, 2024

Context

Runtime tests got moved over to this repo and expanded upon it seems. Originally eoapi-k8s copy pasta'd them to make sure things worked across cloud providers. Now given #86 there's a potential third repo that tests might need to get

Goal

Document which tests we have for eoapi-devseed and eoapi-k8s. Make decisions about which ones eoepca+ needs. Then come up with a plan to "reuse" just the tests as much as possible between the projects where they need to be reused

AC

  • google doc matrix of tests between eoapi-devseed and eoapi-k8s
  • ask around about ideas for sharing
  • decide how to share and expand next ACs
@ranchodeluxe ranchodeluxe self-assigned this Jun 18, 2024
@vincentsarago
Copy link
Member

the tests were moved to eoapi-devseed because they were testing the custom runtimes, not the classic eoAPI building blocks.

we could design tests for the raster/stac/vector API, but those should and are already well tested individually on their own repo.

@ranchodeluxe
Copy link
Contributor Author

we could design tests for the raster/stac/vector API, but those should and are already well tested individually on their own repo.

yeah, we don't need all the tests just s subset of them working for eoapi-k8s and then reused on eoepca+ is how I see this now. Copy pasted for now between eoapi-k8s and eoepcia+. Will break out into a package later.

But I believe these are needed b/c they've been pretty useful to have for testing out SSL, traefik and nginx rewrite capabilities to know when the proxy settings are misaligned 👍

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

No branches or pull requests

2 participants