Wednesday 25th September, 2013
8:30am to 9:30am
For years Red Hat has been exploring how to layer and separate its code to test it in isolation on the unit level. It has kept integration and functional testing as a big ball of mud, jumping straight from unit to full system testing. But could it apply some of the same lessons learned from unit testing to integration testing? This session explores the different technologies within the enterprise Java specification and shows how Red Hat’s application could be tested in isolation; layer for layer, module for module, and component for component. Is it possible to isolate and stay real at the same time? Do mocks, stubs, and test doubles have a place in the world of integration testing? Are there other lessons to be learned?
Hilton - Continental Ballroom 5
Java Engineer | Developer Advocate and Program Manager at @RedHatSoftware | Author of @ContinuousDev from @OReillyMedia | Devoted Grandmother of five. bio from Twitter
Arquillian Project Lead, Senior Software Engineer at Red Hat, O'Reilly Author http://shop.oreilly.com/product/063692…, JavaChampion bio from Twitter
Sign in to add slides, notes or videos to this session