• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Working with WSDL Documents
• Chapter 13: Building XML Pipelines
  • What is an XML Pipeline?
  • The XML Pipeline Editor
  • Steps for Building an XML Pipeline
  • Planning an XML Pipeline
  • Use Case: Building order.pipeline
    • order.pipeline Requirements
    • Getting Started: Creating a New XML Pipeline
    • XML Pipeline Scenarios
    • Specifying an Execution Framework
    • Configuring Data Sources
    • Using XQuery to Merge Source File Data
    • Adding an XQuery Node
    • Setting the XQuery Node Data Sources
    • Testing the XML Pipeline
    • Setting a Value for an Output Port
    • Designing a Report from the XML Document
    • Adding XSLT and XQuery Transformations
    • Finishing Up
  • Working with Nodes
  • Working with the XML Pipeline Diagram
  • Debugging an XML Pipeline
  • Generating Code for an XML Pipeline
  • XML Pipeline Node Properties Reference
• Chapter 14: Publishing XML Data
• Chapter 15: Integrating with Third-Party File Systems
• Chapter 16: Extending Stylus Studio
• Chapter 17: The Stylus Studio Java API
• Chapter 18: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > Testing the XML Pipeline

Testing the XML Pipeline

The XML pipeline as it is defined now creates an XML document containing a book parent node, with title, quantity, and ISBN child nodes. Let's test it before continuing.

To test an XML pipeline, click the Execute button ( ):

In this case, Stylus Studio displays a message indicating that the XML pipeline, as it is currently defined, does not have an output. And if we examine our XML pipeline, we see that this is true - processing terminates with the XQuery node, but its output port is empty.