Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange timeout value printed when using SelenideAddons.wrapAssertionError() #101

Closed
jowerner opened this issue Aug 29, 2019 · 0 comments
Closed
Assignees
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

Comments

@jowerner
Copy link

See below for a stack trace created using SelenideAddons.wrapAssertionError():

UIAssertionError AssertionError: null
Screenshot: file:/D:/workspace/neodymium-template/build/reports/tests/1567080799625.0.png
Page source: file:/D:/workspace/neodymium-template/build/reports/tests/1567080799625.0.html
Timeout: 1567080799.620 s.
Caused by: java.lang.AssertionError
	at com.codeborne.selenide.ex.UIAssertionError.wrapThrowable(UIAssertionError.java:58)
	at com.codeborne.selenide.ex.UIAssertionError.wrap(UIAssertionError.java:54)
	at com.xceptance.neodymium.util.SelenideAddons.wrapAssertionError(SelenideAddons.java:278)
	at template.pageobjects.pages.HomePage.isExpectedPage(HomePage.java:32)
	at template.neodymium.tests.smoke.HomePageTest.testVisitingHomepage(HomePageTest.java:20)

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).

@jowerner jowerner modified the milestone: v3.4.0 Aug 29, 2019
@occupant23 occupant23 self-assigned this Aug 29, 2019
@occupant23 occupant23 added bug codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there Low Priority labels Aug 29, 2019
@occupant23 occupant23 added this to the v3.4.0 milestone Aug 29, 2019
@jowerner jowerner added the codeDone The issue is rechecked for development branch label Aug 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants