GITB TDL Documentation

Welcome to the documentation of the GITB Test Description Language (TDL). The GITB TDL is used to define test cases to realise a specification’s conformance testing needs. This documentation provides a reference for all concepts and constructs involved in the definition of test cases, as well as code snippets and guidelines to use during test development.

Table of contents

• Introduction
  • What is the GITB TDL?
    • Where is it used?
    • How is it maintained?
  • Core concepts
    • Test case
    • Test suite
    • Test session
    • Test session context
    • Actor
    • Messaging handlers
    • Validation handlers
    • Processing handlers
  • The lifecycle of a test session
    • Step 1: Create
    • Step 2: Configure
    • Step 3: Initiate
    • Step 4: Run preliminary
    • Step 5: Run test steps
    • Step 6: Finalise
    • Step 7: Consult
  • Specification links
• Test suites
  • Overview
  • Elements
    • Metadata
    • Actors
    • Test cases
  • Deploying a test suite in the GITB software
  • Sharing resources across test suites
    • Test suites as shared resource holders
• Test cases
  • Overview
  • Elements
    • Metadata
    • Namespaces
    • Imports
    • Preliminary
    • Actors
    • Variables
    • Steps
    • Output
    • Scriptlets
• Scriptlets
  • Overview
  • Elements
    • Metadata
    • Namespaces
    • Imports
    • Params
    • Variables
    • Steps
    • Output
  • Dynamic presentation within scriptlets
  • Dynamic steps within scriptlets
  • Scriptlets embedded in test cases
• Types
  • Map variables
  • List variables
  • Type conversions
• Expressions
  • Escaping XML in expressions
  • Referring to variables
    • Map elements
    • List variable elements
    • Missing variables
  • Defining variables from expressions
  • Referring to configuration parameters
    • Domain configuration parameters
    • Organisation configuration parameters
    • System configuration parameters
    • Actor configuration parameters
  • Accessing test session metadata
  • Checking the result of test steps
    • Checking whether a specific step succeeded
    • Checking the current result of a test session
    • Checking the status of a specific step
    • Status checks for scriptlet steps
  • Expressions and templates
  • Where can expressions be used?
• TDL step constructs
  • Overview
  • Messaging steps
    • btxn
    • etxn
    • listen
    • receive
    • send
  • Processing steps
    • bptxn
    • eptxn
    • process
  • Flow steps
    • exit
    • flow
    • foreach
    • if
    • repuntil
    • while
  • Support steps
    • assign
    • call
    • group
    • interact
    • log
    • verify
  • Common step concepts
    • Rich documentation per step
    • Stop a test session upon errors
    • Hide test steps
    • Collapse sets of test steps
• Service handlers
  • Specifying the handler implementation
  • Embedded handlers
    • Embedded messaging handlers
    • Embedded processing handlers
    • Embedded validation handlers
  • Authentication for external handlers
  • Handler inputs and outputs
• Examples
  • Example 1: Invoice validation via user upload
  • Example 2: Invoice validation via direct AS2 messaging
  • Example 3: Invoice validation via direct AS4 messaging
  • Example 4: Invoice validation via AS2 with automatic discovery
  • Example 5: ESPD content validation via user upload
  • Example 6: WMS client request validation
  • Example 7: ASiC container validation for eTendering processes
• Change history
  • What’s new in release 1.20.0
  • Previous documentation versions
• Index