-
Notifications
You must be signed in to change notification settings - Fork 14
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
Feature/fix xpath matcher #555
Conversation
roesslerj
commented
Dec 5, 2019
- the code follows the Clean Code guidelines.
- the necessary tests are either created or updated.
- all status checks (Travis CI, SonarCloud, etc.) pass.
- your commit history is cleaned up.
- you updated the changelog.
- you updated necessary documentation within retest/docs.
Cool, this partly adresses retest/recheck-web#132 (see retest/recheck-web#132 (comment)). |
@@ -26,7 +29,7 @@ public boolean test( final Element element ) { | |||
|
|||
@Override | |||
public String toString() { | |||
return String.format( ElementXpathMatcherLoader.FORMAT, xpath ); | |||
return String.format( ElementXpathMatcherLoader.FORMAT, "/" + xpath ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The leading slash is correct for the absolute XPath, but this doesn't correspond to our internal representation I guess? Is this good?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we should think about changing our internal representation. But this is definitely a separate PR...
07f2782
to
d6d3dd4
Compare