Java Day Kharkiv - Integration Testing from the Trenches Rebooted

transcript

INTEGRATION TESTING FROM THE TRENCHESREBOOTED@NICOLAS_FRANKEL

https://leanpub.com/integrationtest/ 2

ME, MYSELF AND I

FROM THE BOOK

4https://leanpub.com/integrationtest/

INTRODUCTION

INTEGRATION TESTING FROM THE TRENCHES - REBOOTED

TESTING?Unit TestingMutation TestingGUI TestingPerformance Testing• Load Testing• Stress Testing• Endurance Testing

Security Testingetc.

UNIT VS. INTEGRATION TESTINGUnit Testing• Testing a unit in isolation

Integration Testing• Testing the collaboration of

multiple units

EXAMPLEA prototype car

UNIT TESTINGAkin to testing each nut and bolt separately

INTEGRATION TESTINGAkin to going on a test drive

UNIT + INTEGRATION TESTINGTake a prototype car on a test drive having tested only nuts and bolts?Manufacture a car having tested nuts and bolts but without having tested it on numerous test drives?

SYSTEM UNDER TESTSUT is what get testedTechniques from Unit Testing can be re-used•Dependency Injection• Test doubles

REMINDER: TEST DOUBLESDummyMockStubSpyFake

TESTING IS ABOUT ROIThe larger the SUT• The more fragile the test• The less maintainable the

test• The less the ROI

TESTING IS ABOUT ROITests have to be organized in a certain way• The bigger the SUT• The less the number of

TESTING IS ABOUT ROIIntegration Testing• Test nominal cases

INTEGRATION TESTING CHALLENGES

INTEGRATION TESTS CHALLENGESSlowFragileHard to diagnose

Y U SLOW?Use infrastructure resourcesUse container

COPING WITH SLOWNESSSeparate Integration Tests from Unit Tests

INTEGRATION TESTS ARE STILL SLOWSeparating IT doesn’t make them fasterBut errors can be uncovered faster• Fail fast• It will speed testing

HOW TO SEPARATE?Depends on the build tool•Ant•Maven•Gradle• Something else?

REMINDER: MAVEN LIFECYCLE

compiletest package

integration-test

pre-integration-test

verifypost-in

tegration-test

compiler:compile

surefire:test

MAVEN SUREFIRE PLUGINBound to the test phaseRuns by default•*Test•Test*•*TestCase

MAVEN FAILSAFE PLUGIN“Copy” of SurefireDifferent defaults•*IT•IT*•*ITCase

MAVEN FAILSAFE PLUGINOne goal per lifecycle phase• pre-integration-test• integration-test• post-integration-test• verify

Must be bound explicitly

POM SNIPPET<plugin> <artifactId>maven-failsafe-plugin</artifactId> <version>2.17</version> <executions> <execution> <id>integration-test</id> <goals> <goal>integration-test</goal> </goals> <phase>integration-test</phase> </execution> <execution> <id>verify</id> <goals> <goal>verify</goal> </goals> <phase>verify</phase> </execution> </executions></plugin>

CONTINUOUS INTEGRATIONUnit Tests run at each commitIntegration Tests run “regularly”• Daily• Hourly• Depending on the context

Y U FRAGILE?Usage of infrastructure resources• External•Multiple

INFRASTRUCTURE RESOURCESFile systemTimeDatabasesWeb ServicesMail serversFTP Serversetc.

TIME/FILE SYSTEM:COPING WITH FRAGILITY

Use Dependency InjectionUse abstractions• e.g. java.nio.file.Path instead of java.util.File

DATABASES:COPING WITH FRAGILITY

Test the Service layer•Mock the repository

Test the Repository layer•Mock the database???

DATABASES:COPING WITH FRAGILITY

Use Fakes under your control

ORACLE DATABASE USE-CASEUse an in-memory data source and hope for the bestUse Oracle Express and hope for the bestUse a dedicated remote schema for each developer• And your DBAs will hate you

TRADE-OFFThe closer to the “real” infrastructure,the more complex the setup

MANAGING THE GAP RISKIn-memory databases are easy to setuph2 is such a database• Compatibility modes for

most widespread DB• jdbc:h2:mem:test;MODE=Oracle

WEB SERVICES:COPING WITH FRAGILITY

Web Services as infrastructure resources• Hosted on-site• Or outside

Different architectures• REST(ful)• SOAP

WEB SERVICES:COPING WITH FRAGILITY

Use Fakes under your control

FAKE RESTFUL WEB SERVICESSpark•Micro web framework•A la Sinatra•Very few lines of code• Just serve static JSON files

SPARK SAMPLEimport static spark.Spark.*;import spark.*;

public class SparkSample{ public static void main(String[] args) { setPort(5678); get("/hello", (request, response) -> { return "Hello World!"; }); get("/users/:name", (request, response) -> { return "User: " + request.params(":name"); }); get("/private", (request, response) -> { response.status(401); return "Go Away!!!"; }); }}

FAKE SOAP WEB SERVICESPossible with Spark• But not efficient• Remember about ROI

SMARTBEAR SOAPUI

SMARTBEAR SOAPUIHas a GUIGood documentationUnderstands•Authentication•Headers• Etc.

SOAPUI USAGEGet WSDL• Either online• Or from a file

Create MockService• Craft the adequate response

Run the servicePoint the dependency to localhost

CHALLENGES TO THE PREVIOUS SCENARIOCraft the adequate response?• More likely get one from the real WS• And tweak it

Running in an automated way• Save the project• Get the SOAPUI jar• Read the project and launch

SOAPUI APIWsdlProject project = new WsdlProject();String wsdlFile = "file:src/test/resources/ip2geo.wsdl";WsdlInterface wsdlInterface = importWsdl(project, wsdlFile, true)[0];WsdlMockService fakeService = project.addNewMockService("fakeService");WsdlOperation wsdlOp = wsdlInterface.getOperationByName("ResolveIP");MockOperation fakeOp = fakeService.addNewMockOperation(wsdlOp);MockResponse fakeResponse = fakeOp.addNewMockResponse("fakeResponse");fakeResponse.setResponseContent( "<soapenv:Envelope ...</soapenv:Envelope>");runner = fakeService.start();

FAKING WEB SERVICE IN REAL-LIFEUse the same rules as for UT• Keep validation simple• Test one thing

Keep setup simple• Don’t put complex logic• OK to duplicate setup in each test

• Up to a point

IN-CONTAINER TESTING

INTEGRATION TESTINGCollaboration between classesBoundaries with external dependenciesWhat did we forget?

DEPENDENCIESThe most important dependency is the container!• Spring• Java EE•Application server

SPRING CONFIGURATION TESTINGSo far, we can test:• Beans whose dependencies

can be mocked• Beans that depend on fake

resourcesWhat about the configuration?

DESIGNING TESTABLE CONFIGURATIONConfiguration cannot be monolithic• Break down into fragments• Each fragment contains a set

of either• Real beans• Fake beans

EXAMPLE: DATASOURCE CONFIGURATIONProduction JNDI fragmentTest in-memory fragment

EXAMPLE: DATASOURCE CONFIGURATION@Beanpublic DataSource ds() { JndiDataSourceLookup lookup = new JndiDataSourceLookup(); lookup.setResourceRef(true); return lookup.getDataSource("jdbc/MyDS");}

@Beanpublic DataSource ds() { org.apache.tomcat.jdbc.pool.DataSource ds = new org.apache.tomcat.jdbc.pool.DataSource(); ds.setDriverClassName("org.h2.Driver"); ds.setUrl("jdbc:h2:~/test"); ds.setUsername("sa"); ds.setMaxActive(1); return ds;}

FRAGMENT STRUCTURE Main fragment• Repository• Service• etc.

Prod DB fragment Test DB fragment

TIPSPrevent coupling• Use top-level assembly instead of

fragment referencesPool exhaustion check• Set the maximum number of

connections in the pool to 1Compile-time safety• Use JavaConfig

NOW, HOW TO TEST?Spring Test• Integration with

widespread testing frameworks

SAMPLE TESTNG TEST WITH SPRING@ContextConfiguration( classes = { MainConfig.class, TestDataSourceConfig.class })@RunWith(SpringJUnit4ClassRunner.class)public class OrderIT {

@Autowired private OrderService orderService;

@Test public void should_do_this_and_that() { orderService.order(); Assert.assertThat(...) }}

TESTING WITH THE DATABASETransactions• Bound to business feature• Implemented on Service

layer•@Transactional

TRANSACTION MANAGEMENT TIPWhen tests fail•How to audit state?• Spring rollbacks

transactions@Commit

TRANSACTION MANAGEMENT SAMPLE@ContextConfiguration@Transactional@Commit@RunWith(SpringJUnit4ClassRunner.class)public class OverrideDefaultRollbackSpringTest{

@Test @Rollback public void transaction_will_be_rollbacked() { ... }

@Test public void transaction_will_be_committed() { ... }}

END-TO-END TESTING?Testing from the UI layer is fragile•UI changes a lot

URL not so much

MOCKMVC“Main entry point for server-side Spring MVC test support”

MOCKMVC SAMPLEmockMvc.perform(get("/")) .andExpect(status().isOk()) .andExpect(view().name("welcome"));

SPRING BOOT

SPRING BOOT@AutoConfigureMockMvcInject MockMvc

SPRING BOOT@SpringBootTest instead of @ApplicationContext

SPRING BOOT LAYERED TESTSJPA•@DataJpaTest

Web•@WebMvcTest•@MockBean

http://blog.frankel.ch/@nicolas_frankel http://frankel.in/https://git.io/viPPz

Java Day Kharkiv - Integration Testing from the Trenches Rebooted

Software