Full integration tests #9
Comments
vasco-santos
added
P0
This was referenced Jan 11, 2023
vasco-santos
added a commit
that referenced
this issue
Jan 13, 2023
Adds integration tests with `w3up-client` to test: - ucanto flows for `store/add`, `upload/add`, `upload/remove` and `upload/list` by using `client.uploadFile`, `client.capabilities.remove` and `client.capabilities.list` - add to DUDEWHERE on `upload/add` happens Other details: - New environmental variable for local integration tests added - CI secrets setup according to https://gist.github.com/alanshaw/e949abfcf6728f590ac9fa083dba5648 and added in 1password - set seed.run CI to node18 to be able to use w3up-client in CI Decisions made: - we rely on random CAR generation to guarantee that always new things are written (in dudewhere for example). This will mean that we will end up with a lot of content generated in CF staging buckets by dudewhere and replicator for these tests. We should as follow up look into automate a GC for staging resources Second part of #9
vasco-santos
added a commit
that referenced
this issue
Jan 17, 2023
Adds integration tests for remaining sst stacks. It includes: - Check carpark bucket got car file written into - Check satnav stack did its thing and created side index file for uploaded CAR - Check replicator did its thing, getting CAR replicated to CF carpark, as well as satnav side index Needs: - [x] Follow up of #125 Closes #9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As follow up from #4 , we need to look into having proper integration tests running the API Stack.
This can be decoupled in:
store/*andupload/*flows with w3up-client + using access test: integration tests with w3up client #125The text was updated successfully, but these errors were encountered: