Look into removing or simplifying xsltproc requirement

[gbirchmeier]

All xsltproc does is create a pretty html-ized output for UTs.

It's kind of annoying to install on Windows because of its dependencies.

I think it'd be good if we can either remove it or make it really easy to install.

One possible option: Use Ruby (with or without a gem) to do xsltproc's job. Since tests are mainly going to be run by people hacking on QF/n, and those developers will already have Ruby, I see no big downside to this (aside from increasing our reliance on Ruby).

[unclepaul84]

I just wrote a .Net based drop-in replacement for xsltproc. it has no dependecies, besides .NET framework. I tested it with the unit test runner script.

See http://unclepaul84.blogspot.com/2012/10/net-equivalent-of-xslproc.html for code.

[gbirchmeier]

That's pretty cool. If I were to use this, would I just drop in the compiled exe?

[unclepaul84]

Yep.

Furthermore, I don't think you would want to assume that it is in the
system PATH in your test script (i would put it in resources and have the
relative path point there), that way installation is much simpler.

2012/10/8 Grant Birchmeier [email protected]

That's pretty cool. If I were to use this, would I just drop in the
compiled exe?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/104#issuecomment-9240842.

[cbusbey]

• remove xslt execution calls
• remove legacy xslt templates
• remove reference in readme