When test fails, Selenide should report **exact** actual value at the moment of failure

[asolntsev]

Now it's possible that condition is not met at the moment when Selenide checks it. But at the moment of reporting error condition can be met. For example, this error message is misleading:

com.codeborne.selenide.ex.ElementShould: Element should have textCaseSensitive '09000525 FD: 1999-11-08' {.timeline-event-bubble-title}
Element: '<div class="timeline-event-bubble-title">09000525 FD: 1999-11-08</div>'
    at com.codeborne.selenide.impl.AbstractSelenideElement.checkCondition(AbstractSelenideElement.java:512)
    at com.codeborne.selenide.impl.AbstractSelenideElement.should(AbstractSelenideElement.java:476)
    at com.codeborne.selenide.impl.AbstractSelenideElement.invokeShould(AbstractSelenideElement.java:299)
    at com.codeborne.selenide.impl.AbstractSelenideElement.dispatchSelenideMethod(AbstractSelenideElement.java:179)
    at com.codeborne.selenide.impl.AbstractSelenideElement.dispatchAndRetry(AbstractSelenideElement.java:92)
    at com.codeborne.selenide.impl.AbstractSelenideElement.invoke(AbstractSelenideElement.java:67)
    at com.codeborne.selenide.impl.WaitingSelenideElement.invoke(WaitingSelenideElement.java:18)
I think that Selenide can be more "smart" and remember the stringified DOM element each time before checking the condition, so that when condition fails the error message is not contradictory.