You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The failure renderer should be extended to tolerate when no description.getTestClass() is provided. As a fallback it could look into the stack trace and detect the first instrumented method.~~
Cucumber does not support JUnit Rules, so it can only be used with the ScottRunListener. This should be documented in the cucumber example. The listener simply writes to system.out, which is really ugly. Maybe it should modify the original exception?
The changes described above has been applied, but they just brought new problems to the surface:
Now the source code for the glue code is found, but it reports the exception one line after the method body.
Cucumber reports are not altered if the exception message is modified in the Run Listener, so I doubt they would be the optimal solution for this problem. Try a custom Cucumber Formatter for this instead.
The Cucumber Runner saves the exception message in its
Result object before Scott could enhance it.
The Exception object is available for the Formatters, but by default
they use the saved text instead.
This problem is fixed with the usage of custom Cucumber Formatters. See scott-example-cucumber project for more info.
No description provided.
The text was updated successfully, but these errors were encountered: