If Oxygen has a test coverage feature for XSpec that shows all the
lines visited, you could write an XSpec test with the context set to
your chosen input file and then 'run test with coverage', rather than
the normal run method.
I'm designing a solution for another XSLT editing solution that will
provide for this 'run test with coverage', but I'm hoping to add a
dedicated feature that doesn't require a test, just a context file.
The output should show each XSLT file with green highlights on the
line numbers in the margin for executed lines and red highlights where
code was executable not invoked. The templates that you can eliminate
will therefore be easy to recognise. The intention is to make this a
cumulative view, so you can perform multiple runs, selecting a new
input each time, until you've covered all the scenarios you need to
continue supporting.
On Thu, Oct 22, 2026 at 3:31b/PM rick@xxxxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Hi All,
>
>
>
> I have a rather lengthy stylesheet that I have modified for different, but
similar content. I want to locate templates that are being processed during
the transformation so I can eliminate those that arenbt being used.
>
>
>
> I am using Saxon EE within Oxygen for my transformations.
>
>
>
> Thank you,
>
> Rick Quatro
>
> XSL-List info and archive
> EasyUnsubscribe (by email)