Details
-
Bug
-
Resolution: Fixed
-
Major
-
15.3-rc-1, 14.10.8
-
Unknown
-
N/A
-
N/A
-
-
org.xwiki.flamingo.test.docker.AllITs$NestedFormTokenInjectionIT#simpleRESTPost{TestUtils, TestReference}
Description
Error:
org.opentest4j.MultipleFailuresError: Multiple Failures (4 failures) java.lang.AssertionError: Expected: a string containing "Request with init: 201" but: was "Simple POST: 201Only Request: 201Request Body" java.lang.AssertionError: Expected: a string containing "Simple with array headers: 201" but: was "Simple POST: 201Only Request: 201Request Body" java.lang.AssertionError: Expected: a string containing "Request with init body" but: was "Simple POST: 201Only Request: 201Request Body" java.lang.AssertionError: Expected: a string containing "Simple with array headers body" but: was "Simple POST: 201Only Request: 201Request Body"
Stacktrace:
at org.junit.jupiter.api.AssertAll.assertAll(AssertAll.java:80) at org.junit.jupiter.api.AssertAll.assertAll(AssertAll.java:58) at org.junit.jupiter.api.Assertions.assertAll(Assertions.java:2980) at org.xwiki.flamingo.test.docker.FormTokenInjectionIT.simpleRESTPost(FormTokenInjectionIT.java:64)
Alternatively, the failure happens also with just two of the four failures.
The reason is most likely that the page ready feature doesn't wait long enough for the next request to be triggered. While the screenshot shows indeed the missing text, the video shows that with some delay the remaining requests return and all expected text is displayed. The test should be made more robust by waiting for the text to appear.
Attachments
Issue Links
- is caused by
-
XWIKI-20135 No CSRF protection on REST API
- Closed