IT tests are lacking snapshots on failure #23
Assignees
Comments
denis-anisimov
pushed a commit
that referenced
this issue
Sep 9, 2021
Quarkus integration tests should be used instead of unit tests. Screenshot on failure extension is added. fixes #23
9 tasks
denis-anisimov
pushed a commit
that referenced
this issue
Oct 5, 2021
Quarkus integration tests should be used instead of unit tests. Screenshot on failure extension is added. fixes #23
denis-anisimov
pushed a commit
that referenced
this issue
Oct 6, 2021
Quarkus integration tests should be used instead of unit tests. Screenshot on failure extension is added. fixes #23
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Quarkus ITs are based on Junit5 which doesn't support
@Rules.The
ScreenshotOnFailureRuleobject which is used in the base abstract test for quarkus ITs doesn't do anything since it's Junit 4 Rule (and as said above the test is executed using Junit5 without Rules support).As a result : if test is failing there is no any way to check what's going on there.
The screenshots support should be done for quarkus ITs using Juni5 API somehow.
The text was updated successfully, but these errors were encountered: