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
- use x:output-expect from v0.3.0 to fix regression bugs in #26#30#33
- remove attributes assert and context of x:expect as assert seems a duplicate of test and there is no documentation on how these attributes should behave
- in the test suite remove x:expect for tests using attribute assert as they are all duplicates of test
- add more tests to cover #26#30#33
* revert to x:output-expect from v0.3.0 #26#30#33
- use x:output-expect from v0.3.0 to fix regression bugs in #26#30#33
- remove attributes assert and context of x:expect as assert seems a duplicate of test and there is no documentation on how these attributes should behave
- in the test suite remove x:expect for tests using attribute assert as they are all duplicates of test
- add more tests to cover #26#30#33
test.xsl (just returns the input node intact)
test_old.xspec (tests test.xsl by looking for
descendant::baz
)x:expect label="Expect failure"
is expected to fail, because of the text node difference.With XSpec 0.3.0, the failure report HTML is generated as follows. (Indent and xmlns omitted for brevity)
<baz>original-text</baz>
<baz>broken-text</baz>
So far, so good.
XSpec 0.4.0-RC changed the recommended way to describe the same
x:expect
. (Just my guess... Any clarification or documentation welcomed.)test_new.xspec (
test
attribute in test_old.xspec is replaced withcontext
attribute)Running this scenario with the latest master, the failure report HTML is generated as follows. (Indent omitted for brevity)
<foo><bar><baz>original-text</baz></bar></foo>
<baz>broken-text</baz>
Notice the left-hand Result is the entire result, not
<baz>original-text</baz>
which 0.3.0 used to report.The text was updated successfully, but these errors were encountered: