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
Open an XSpec test for a Schematron schema in which a scenario contains <x:expect-valid> and <x:expect-assert>.
Duplicate the <x:expect-assert>, including all its attributes, in the same XSpec file. For instance, copy the element and paste it into another scenario.
Click Run XSpec test scenarios to run the test.
In the XSpec Test Results window, click Show next to the listing for valid. The <x:expect-valid> element should be selected, but it isn't.
Click Show next to each of the <x:expect-assert> elements. They both select the first instance of this element in the XSpec file, instead of selecting the corresponding instance.
The issue with <x:expect-assert> seems to affect <x:expect-report>, <x:expect-not-assert>, <x:expect-not-report>, and <x:expect-rule> as well.
(Perhaps everything fails in the example above, depending on your schema, but I don't think the pass/fail status affects the "Show" behavior I'm seeing.)
The text was updated successfully, but these errors were encountered:
At first, I thought this issue was Schematron-specific and did not affect <x:expect> in a test for XSLT or XQuery. I changed my mind. In the sample code below in a test for XSLT or XQuery, the duplicate scenario labels (in addition to duplicate <x:expect> elements) seem relevant.
How to reproduce the problem in Oxygen 26.1:
<x:expect-valid>
and<x:expect-assert>
.<x:expect-assert>
, including all its attributes, in the same XSpec file. For instance, copy the element and paste it into another scenario.<x:expect-valid>
element should be selected, but it isn't.<x:expect-assert>
elements. They both select the first instance of this element in the XSpec file, instead of selecting the corresponding instance.The issue with
<x:expect-assert>
seems to affect<x:expect-report>
,<x:expect-not-assert>
,<x:expect-not-report>
, and<x:expect-rule>
as well.Sample XSpec scenarios, just to make it concrete
(Perhaps everything fails in the example above, depending on your schema, but I don't think the pass/fail status affects the "Show" behavior I'm seeing.)
The text was updated successfully, but these errors were encountered: