XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Feature Requests » XSLT Unit Testing
Conferences Close Tree View
- Stylus Studio Feature Requests (1192)
-> - Proposal to Add Git Support to... (1)
-> + XML formatter option request (3)
-> - Could Pipeline input scenario ... (1)
-> + XML Traversal in XSLT Mapper (2)
-> + Email not in HTML as expected (3)
-> + My SS Open [tools]==>.[option... (3)
-> + Fonts in Stylus Studio (2)
-> - Fix the check for concurrent s... (1)
-> + Stylus is showing the error fo... (2)
-> - XML editor (1)
-> + Unable to see filename in sche... (2)
-> + Unable to connect to JVM (2)
-> - Stylus Studio forum questions (1)
-> + User Interface - X16 Enterpris... (2)
-> + Stylus Studio High DPI support (2)
-> + target xsd includes and import... (2)
-> + XML/EDIFACT Schema (3)
-> + Options to control whether BOM... (2)
-> + Snippets and/or Emmet integrat... (2)
-> + internal error accessing metho... (2)
-- [1-20] [21-40] [41-60] Next
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Neal WaltersSubject: XSLT Unit Testing
Author: Neal Walters
Date: 08 May 2006 04:39 PM
I've recently been studying NUnit, a unit testing tool for .NET.

I'm thinking about how to write NUnit tests for XSLT, it probably won't be that difficult.

I've got a few complex XSLT's, and it seems like when we fix one problem, we often break something else.

But, have you thought about including unit testing totally inside of Stylus Studio. For example, you can flag a "Scenario" as a unit test.
We could create 10 different inputs, and eventually save 10 files as "ok" or approved outputs. (Or even more sophisticated would be some type of Xpath tests to validate the output - rather than validating the entire file).

Then when you change the XSLT source code, you would click a button that would say "Run all unit test scenarios". Any scenarios that have non-matching outputs would show in red, all the good ones in green.

Neal Walters
http://Biztalk-Training.com
http://DotNet-AddOns-Training.com (Nunit/Nant/FxCop/NDoc/etc)



Postnext
ad van der endeSubject: XSLT Unit Testing
Author: ad van der ende
Date: 21 Jun 2006 07:22 AM
Yes, yes, yes, please asap.
Posttop
Minollo I.Subject: XSLT Unit Testing
Author: Minollo I.
Date: 21 Jun 2006 09:00 AM
This is an interesting idea; the same could be easily applied to other Stylus Studio modules. We will see what we can do about this.

Thanks!
   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.