Testing Microservices with a Citrus twist
•
1 like•2,871 views
This document discusses Citrus, an open source integration test framework for automated interface testing of distributed systems. It focuses on testing message exchanges between services. The presentation provides an overview of Citrus capabilities such as ready-made endpoint components for REST, JMS, SOAP and others. It demonstrates how to write Citrus tests using actions like send, receive and validate messages. Integration with tools like Docker, Camel and Arquillian is also highlighted. The document concludes with information on learning more about Citrus.
Recommended
More Related Content
What's hot
What's hot (18)
Viewers also liked
Viewers also liked (20)
Similar to Testing Microservices with a Citrus twist
Similar to Testing Microservices with a Citrus twist (20)
Recently uploaded
Recently uploaded (20)
Testing Microservices with a Citrus twist
- 1. @citrus_test#Devoxx #CitrusTwist Testing Microservices with a Citrus Twist Christoph Deppisch ConSol* Software GmbH
- 2. @citrus_test#Devoxx #CitrusTwist Christoph Deppisch • Senior software developer • @ConSol* Munich, Germany • 10 years of experience in Java • Passionate about automated software testing • Founder of the Open Source framework Citrus • Happy to be here today! Twitter: @freaky_styley
- 3. @citrus_test#Devoxx #CitrusTwist What is Citrus? • Open Source integration test framework • Focus on messaging in distributed software systems • Automated interface tests • Ready-to-use endpoint components for message exchange • Works & integrates with well-known libraries • TestNG, JUnit • Apache Camel, Spring, Docker,Arquillian …
- 5. @citrus_test#Devoxx #CitrusTwist Every project needs integration tests!
- 6. @citrus_test#Devoxx #CitrusTwist Service A Service B Interface REST, JMS, File, SOAP
- 7. @citrus_test#Devoxx #CitrusTwist Service A Service B Interface REST, JMS, File, SOAP Mock? Simulator?
- 8. @citrus_test#Devoxx #CitrusTwist Service A Interface REST, JMS, File, SOAP
- 14. @citrus_test#Devoxx #CitrusTwist import com.consol.citrus.annotations.CitrusTest; import com.consol.citrus.dsl.testng.TestNGCitrusTestDesigner; import org.testng.annotations.Test; @Test public class SampleCitrusIT extends TestNGCitrusTestDesigner { @CitrusTest public void sayHello() { echo("Hello, Devoxx! This is my first Citrus test!"); } }
- 16. @citrus_test#Devoxx #CitrusTwist • Missing something? Adding custom actions is possible! Test actions Test action Description echo Log message to console send Sends a message receive Receives a message sleep Wait some time sql Execute SQL statements parallel Execute actions in parallel conditional Execute actions based on condition iterate Execute actions in iteration repeat-on-error Failsafe action execution …
- 17. @citrus_test#Devoxx #CitrusTwist @Test public class MessageExchangeIT extends TestNGCitrusTestDesigner { @Autowired private Endpoint orderEndpoint; @CitrusTest public void sendAndReceiveMessage() { send(orderEndpoint) .payload("..."); receive(orderEndpoint) .payload("..."); } }
- 18. @citrus_test#Devoxx #CitrusTwist @CitrusTest public void sendAndReceiveMessage() { variable("orderId", Functions.randomNumber(10L)); send(orderEndpoint) .payload("<order>" + "<id>${orderId}</id>" + "</order>") .header("operation", "placeOrder") .header("id", "${orderId}"); receive(orderEndpoint) .payload("<orderResponse>" + "<timestamp>@ignore@</timestamp>" + "<id>${orderId}</id>" + "<success>true</success>" + "</orderResponse>") .header("id", "${orderId}"); }
- 20. @citrus_test#Devoxx #CitrusTwist • Missing something? Adding custom components is easy! Endpoint components Component Description citrus-http Http REST client and server citrus-jms JMS queue or topic destination citrus-ws SOAP client and server citrus-mail SMTP mail client and server citrus-docker Docker container management citrus-camel Apache Camel endpoint citrus-ftp FTP client and server citrus-vertx Vert.x endpoint citrus-ssh SSH client and server …
- 21. @citrus_test#Devoxx #CitrusTwist <!-- JMS endpoints --> <citrus-jms:endpoint id="orderEndpoint" destination-name="factory.order.inbound"/> <citrus-jms:sync-endpoint id="errorEndpoint" destination-name="base.error.service" timeout="${global.receive.timeout}"/> <!-- JMS connection factory and message broker --> <bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory"> <property name="brokerURL" value="tcp://localhost:61616" /> </bean> Endpoints: citrus-jms
- 22. @citrus_test#Devoxx #CitrusTwist <!-- REST Http client --> <citrus-http:client id="reportingClient" request-method="GET" timeout="5000" request-url="http://localhost:8080/services/report"/> <!-- REST Http server --> <citrus-http:server id="reportingServer" port="8080" auto-start="true"/> Endpoints: citrus-http
- 24. @citrus_test#Devoxx #CitrusTwist Cookie factory sample worker worker worker webapp reporting 2x 4x 1x
- 25. @citrus_test#Devoxx #CitrusTwist Docker infrastructure brokerwebapp report worker worker worker
- 28. @citrus_test#Devoxx #CitrusTwist Demo tools • docker-maven-plugin • docker:build, docker:start, docker:stop • https://github.com/rhuss/docker-maven-plugin • Apache Camel • Content-based routing, REST endpoints, standalone worker • http://camel.apache.org/ • Demo Code • https://github.com/christophd/citrus-demo-devoxx
- 34. @citrus_test#Devoxx #CitrusTwist What else!? • Docker integration • build, start, stop, inspect, … • Manage Docker containers at test runtime • Arquillian extension • Use Citrus in Arquillian test • @CitrusFramework, @CitrusEndpoint, @CitrusResource • Apache Camel integration • Create, start, stop routes at test runtime
- 35. @citrus_test#Devoxx #CitrusTwist Information • Homepage • http://citrusframework.org • Blog • http://labs.consol.de/tags/citrus/ • User Guide • http://citrusframework.org/reference/html/index.html • Mailing List • user@citrusframework.org