Come up with a test plan for the SDK
Opened this issue · 1 comments
At the moment, we have minimal test coverage, particularly on the e2e side.
Come up with a test plan (even if we execute it manually for now), so we can ensure the SDK works as intended.
It does not have to cover all features for now. For example: come up with a plan to test the AWS auth methods. We can add tests for other providers later.
It also does not have to be too sophisticated: it's okay to copy a binary over SSH for example. We just need some rough documented steps we can repeat in case we accidentally introduce a regression (for example as part of #58)
Ideally, we would like have test cases for supported providers and their respective authentication methods
If we do not add these tests to CI/CD, it would be sufficient to have a detailed test guide (or automated test suite) in order to test against these providers/auth methods to catch regressions.