The most convoluted JavaScript testing framework?

Slides from my talk on building a test framework for Mirth Connect channels at JSOxford on the 14th of May 2015 (http://www.meetup.com/JSOxford/events/221556244/). Video available here: https://vimeo.com/127966513

Transcript

1. The most convoluted JavaScript testing framework? Ryan Brooks @spikeheap | ryanbrooks.co.uk
2. Mirth Connect Mirth Connect Appliance VM Our protagonist: Mirth Connect • ETL/integration engine • Java-based *yay* • JavaScript channel definitions Channel Connector Connector
3. • No versioning • No code-completion • No docs in IDE • No refactoring (or any) tools • Manual testing only
4. Solution #1: Jasmine, etc. • No • JavaScript under test has embedded XML
5. Solution #2: Jasmine, on Rhino • No • Rhino’s too old for that kind of jazz
6. Solution #3: Java, FTW • Now we’re getting somewhere • Groovy is like Java, only pleasant
7. Spock
8. We’re not there yet • Equality is important • Always implement equals and hashCode • … or hack dynamic equality on top
9. Bonus points: build system! • Decompile export XML into JS and config files • Compile JS and config files into XML to import • Test on source change
10. Was it worth it?
11. There’s always a way to test it, and generally you should
12. –Me, just now “Building it isn’t enough”
13. Ryan Brooks @spikeheap https://github.com/OxBRCInformatics/mirth-connect-spock https://github.com/spikeheap/groovy-equality-mixin Cheers