Some users reported that gherkin scenario with tablular data render incorrectly in intelliJ. After the test finishes executing a node in the result tree continues to spin. This is likely an error in our implementation of JUnit5. We perhaps forgot to send a signal to alert the framework that the test completed.
Some users reported that gherkin scenario with tablular data render incorrectly in intelliJ. After the test finishes executing a node in the result tree continues to spin. This is likely an error in our implementation of JUnit5. We perhaps forgot to send a signal to alert the framework that the test completed.