Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
5872: Show container logs on update test failure r=MiguelPires a=npepinpe ## Description In the refactoring, it seems I broke showing the container logs when the test fails. This was because the `TestWatcher` extension is called after the resources have been closed, as a `TestWatcher` is supposed to only report on outcomes. I've moved the `onFailure` of the `ContainerState` now to the after test callback, and we can see if it failed by checking if an exception was thrown and not caught during the test. ## Definition of Done _Not all items need to be done depending on the issue and the pull request._ Code changes: * [x] The changes are backwards compatibility with previous versions * [x] If it fixes a bug then PRs are created to [backport](https://github.com/zeebe-io/zeebe/compare/stable/0.24...develop?expand=1&template=backport_template.md&title=[Backport%200.24]) the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. `backport stable/0.25`) to the PR, in case that fails you need to create backports manually. Testing: * [x] There are unit/integration tests that verify all acceptance criterias of the issue * [x] New tests are written to ensure backwards compatibility with further versions * [x] The behavior is tested manually * [ ] The impact of the changes is verified by a benchmark Documentation: * [ ] The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.) * [ ] New content is added to the [release announcement](https://drive.google.com/drive/u/0/folders/1DTIeswnEEq-NggJ25rm2BsDjcCQpDape) Co-authored-by: Nicolas Pépin-Perreault <nicolas.pepin-perreault@camunda.com>
- Loading branch information