Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there
Following on from the conversation on #94, I took a look at the different options for running the tests in CI.
There are a few different ways we could take it:
Rewrite the current tests to mock S3 completely.
In this situation the tests would still look like integration tests but wouldn't actually be testing the storage backend.
Create new unit tests which mock s3, keep the existing integration tests.
note: the integration tests would still not be able to run on CI because they would require the decrypted secrets. If we believe there is value in keeping the integration tests (I do personally) this doesn't get us anywhere unless we introduce a dependency on the maintainers to test PRs.
The plus side of this is we'd get unit tests - but it would require a decent amount of work to add them and doesn't seem strictly related to this problem (would be nice to have regardless)
In this scenario there would be a dependency on the maintainers to run the full suite of tests. This could be done locally or by moving the branch to jdxcode/npm-register where secrets would be decryptable by circle CI
The solution I've included for now is number 3. It's the simplest and unblocks the CI pipeline. Authors of PRs get some feedback on their PR and we are not in a less safe place than we are currently where none of the tests can run.
Would love to get your thoughts on the above @dgautsch @jdxcode