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
However, if the structure is right but the content is wrong, I'm just informed that the XPath was not found. It would be much more comfortable, if I could add matchers to check the xpath result:
I'm trying to verify content that has been rendered in XHTML.
I can do that by looking for an XPath that contains the content, e.g.
assertThat(xhtml, XhtmlMatchers.hasXPath("//ns1:div[@id='content'][text()='Somecontent']", NS1));
However, if the structure is right but the content is wrong, I'm just informed that the XPath was not found. It would be much more comfortable, if I could add matchers to check the xpath result:
assertThat(xhtml, XhtmlMatchers.hasXPath("//ns1:div[@id='content']/text()", NS1, equalTo("Somecontent"));
An error would then show that the content that is wrong.
The text was updated successfully, but these errors were encountered: