Java DSL test actions are not executed immediately. First whole test case is built with actions and then test and all actions get executed at later runtime. This is not intuitive and not straight forward especially for Java developers who are used to having statements that take place immediately.
This design time vs. runtime logic makes writing tests more verbose and difficult to understand when it comes to mix Java DSL action code with custom Java statements. Each custom Java code that is related to test action runtime must be wrapped with custom test action implementation. This leads to more code and less intuitive usage of Java DSL.
Try to remove design and runtime separation for Java DSL test cases.