Friday 4th April, 2014
4:00pm to 4:45pm
For years we’ve been exploring how to layer and separate our
code to test in isolation on the unit level. We’ve kept integration and
functional testing as a big ball of mud; jumping straight from unit to
full system testing. But can we apply some of the same lessons learned
from unit to integration testing?
This session explore the different technologies
within the Java Enterprise specification and see how our application can
be tested in isolation; layer for layer, module for module and
component for component.
Can we isolate and stay real at the same time? Does
mocks, stubs and test doubles have a place in the world of integration
testing? Are there other lessons to be learned?
Arquillian Project Lead, Senior Software Engineer at Red Hat. bio from Twitter
Sign in to add slides, notes or videos to this session