Strange timeout value printed when using SelenideAddons.wrapAssertionError() #101
Labels
bug
codeDone
The issue is rechecked for development branch
codeReadyForRecheck
The issue is fixed/implemented AND merged into development, but needs to be rechecked there
Low Priority
Milestone
See below for a stack trace created using SelenideAddons.wrapAssertionError():
The message text also contains a timeout value. Since a timeout doesn't make sense in this context, Neodymium could set it to 0 (instead of the current time).
The text was updated successfully, but these errors were encountered: