This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Integration test infrastructure #251
Assignees
Comments
This was referenced Mar 26, 2021
|
WIP code for this task is in the https://github.com/paritytech/parity-processbot/tree/jp_companion branch. It's quite far behind so I'll work on porting that to current master. |
Merged
joao-paulo-parity
added a commit
that referenced
this issue
Oct 20, 2021
Adds an integration test and runs it on CI. This PR includes a single simple integration test because its main purpose is to introduce the ability to running integration tests in the first place, since we don't have any. In the future, more integration tests can be added upon the code introduced here. The [original branch](https://github.com/paritytech/parity-processbot/tree/prev-integration-tests) contained a new feature which I've not included here to reduce the scope of this PR and also due to time constraints. closes #251
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Both #250 and #236 bring up issues about flows which entail multiple Github API calls and Webhook Events throughout a single scenario. This project some tests but they are either unit tests or tests which don't exercise a whole scenario for a feature.
This issue is for coming up with an integration test infrastructure which allows for testing the components in unison. The goal is to enable the implementation of whole scenarios with all of its expected interactions, as if it the application were running in production. e.g. for #236 we'll want to purposefully cause a race condition in one of the tests and demonstrate that the application recovers from it.
The text was updated successfully, but these errors were encountered: