Improving developer satisfaction with TDI
summary
Explains Test-Driven Implementation (TDI) and how applying it earlier in the SDLC can speed authoring of FHIR Implementation Guides and FHIR R5 reference implementations/applications. Covers why and when to use TDI, demonstrates creating requirements and FHIR R5 testing artifacts for an Implementation Guide, shows test results for an initial IG version and for a revised IG version tested against the first implementation, and outlines next steps.
AI-written summary · about
related talks
48mTDD: so your code is testable and tested!
45mTDD makes you a better everyday developer
35mIt's a Long Way to the Top (If You Wanna TDD)
32mTDD – Trust Driven Development
35mStrategic TDD
15mIntro to TDD and BDD
45mAccelerate Quality: Building FHIR that Meets Federal Mandates
53mHow to fall in love with TDD
