Teardown not properly executing

[supersilverlemonhaze]

Running the testsuite for a single test case. 3 devices are claimed, one for practitioner and two clients. After the test passes and the teardown happens only 1 device is unclaimed, where it should be 3. Please investigate this issue and make sure unclaims, leaveRooms etc. are all executed as intended.

[Beff42]

Hey there,

for which tests does this happen? It is a continuos issue or sporadic? How can I reproduce this?

Sometimes when severe errors occur during tests executions, we are not able to exit cleanly. This means some resources cannot be deleted/unclaimed. For this reason we do a 'cleanUp call' before every test (see

TI-Messenger-Testsuite/src/main/resources/api/TiMessengerTestTreiber.yaml

Line 102 in 3183663

post:

). You can utilise this internally to delete every remaining resources and unclaim left over devices.
Once the tests are more stable you will see less of this issues. I still highly recommend to implement a cleanUp on your side, since left over resources can affect following tests negatively. Especially when running the full test set, a severe issue in an early test can make test analysis very cumbersome, due to this potential follow-up fails.

[supersilverlemonhaze]

The issue seems to be sporadic. We have only a selected number of test cases enabled from the feature files 0,3,4,5,7 (altogether 13). Cleanup method in DefaultApi is already implemented, but i dont see it being executed anywhere anywhere in the logs, neither it is called from within the testsuite

[Beff42]

The cleanUp call is done with curl. You will see curl calls in the log (look for INFO d.g.t.t.g.a.t.CurlInterceptor - PARALLEL cURL command:) and when you check the RebelLog you will also see the POST calls to /. (the Serenity report itself will not pick them up, because they are executed before the actual test).

Find the RebelLog at the end of the report: