Test driven development I: Introduction
summary
Overview of a working FHIR test ecosystem: a cloud platform called Touchstone executes TestScripts and presents step‑by‑step results, a TestScript resource plus a testing framework formalizes pre‑processing setup, sequential operations and asserts, and optional teardown; the engine can act as client or man‑in‑the‑middle, uses the FHIR validation engine (Java) and supports XPath JSONPath and FHIRPath, optionally runs external Groovy rules via a built‑in compiler, supports eight FHIR versions and keeps historical results and cached capabilityStatements for CI integration.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:34Question...
- 3:33Test Driven Development Philosophy
- 4:17How to integrate TDD into the development lifecycle
- 4:52Test Driven Development with FHIR
- 6:14FHIR Testing Framework - Test Engine Workflow
- 8:22Pre-processing - Capability based testing
- 9:32Test Execution - Operations and Asserts
- 10:59An Operation w/o an Assert is... Well, just an Operation
- 17:20Introducing Touchstone
- 22:53Touchstone Landing Page
- 23:43Getting started with Touchstone
- 25:19Getting started - create a test system
- 28:25Getting started - Test Setup
- 29:19Getting started - Test Execution
- 30:54Getting started - TestScript Execution - Results
- 31:56Analytics are built into Touchstone Conformance
- 34:20Test Execution History
- 34:45Test Driven Development with Touchstone
- 35:14So, how can your organization use Touchstone?
- 36:27Hands on Exercises
related talks
47mLeveraging test-driven development with FHIR implementations
45mAccelerate Quality: Building FHIR that Meets Federal Mandates
46mDevelopment and Testing Strategies
17mFHIR up your tests: Integration tests
46mDIY Testing with Inferno Framework
44mFHIR API Testing with Inferno
44mAPI Testing following the Test Pyramid
48mImproving developer satisfaction with TDI