Testing Java Microservices Workshop
•
11 j'aime•1,645 vues
This document discusses testing microservices and strategies for testing services in a microservices architecture. It covers service virtualization to stub or simulate collaborating services. Contract and consumer-driven testing patterns are explained as well as canary releases, blue-green deployments, and dark launches for releasing to production. Testing strategies like fault injection and monitoring in production environments are also mentioned.
Recommandé
Contenu connexe
Similaire à Testing Java Microservices Workshop
Similaire à Testing Java Microservices Workshop (20)
Plus de Alex Soto
Plus de Alex Soto (17)
Dernier
Dernier (20)
Testing Java Microservices Workshop
- 1. @alexsotob Testing Java Microservices Alex Soto @alexsotob http://www.lordofthejars.com Andy Gumbrecht @AndyGeeDe https://www.tomitribe.com/
- 2. @alexsotob2 https://www.manning.com/books/testing-java-microservices DevoxxUK 2018: ctwdevoxxuk18 (40% off all Manning books and videos)
- 4. S O F T WA R E I S E AT I N G T H E W O R L D
- 5. “With great power, there must also come— great responsibility.” —SPIDERMAN (STAN LEE)
- 6. @alexsotob6
- 7. @alexsotob7
- 9. @alexsotob9 Not talking about traditional tests
- 13. @alexsotob13
- 18. @alexsotob Service Virtualization Capture Mode 18 Service A External Network Service B Scripts Proxy
- 19. @alexsotob Service Virtualization Simulate Mode 19 Service A External Network Service B Scripts Proxy
- 20. @alexsotob20 @Mock EmailService email; Mockito.when(email.receiveBodyMessagesWithSubject("My Subject”)) .thenReturn("This is My Message") // Test calls Mockito.verify(email, Mockito.times(1)) .receiveBodyMessagesWithSubject(Matchers.anyString()); @ClassRule public static HoverflyRule hoverflyRule = HoverflyRule.inSimulationMode(SimulationSource.dsl( service("api.flight.com") .get("/api/bookings/1") .willReturn(success("{"bookingId":"1"}", "application/json")) )); // Test calls hoverfly.verify( service(matches("*.flight.*")) .get("/api/bookings") .anyQueryParams()); Record Method Expectation Verify Method Called Record Service Expectation Verify Service Called
- 23. @alexsotob23 Consumer request response Stub Server expectations Provider request response Result Define Consumer Expectations Verify Expectations On Provider
- 24. @alexsotob24 @RunWith(Arquillian.class) public class CrimesConsumerContractTest { @StubServer URL pactServer; @Pact(provider = "crimes", consumer = "villains") public RequestResponsePact returnListOfCrimes(PactDslWithProvider builder) { return builder .uponReceiving("Gru villain to get all Crimes") .path("/crimes/Gru") .method("GET") .willRespondWith() .status(200) .body(RESPONSE) .toPact(); } @Test @PactVerification("crimes") public void should_get_list_of_crimes_by_villain() { CrimesGateway crimesGateway = new CrimesGateway(webClient, pactServer); final Single<JsonArray> gruCrimes = crimesGateway.getCrimesByVillainName("Gru"); } Stub/proxy Server URL Defines service interaction Provides predefined Req/Res Executes real requests Consumer side
- 25. @alexsotob25 @RunWith(Arquillian.class) @Provider("crimes") @ContractsFolder("~/crimescontract") public class CrimesContractTest { @ArquillianResource Target target; @Test public void should_validate_contract() { assertThat(target).withUrl(getCrimesServer()).satisfiesContract(); } } Provider under validation Location of contracts Http Client Asserts All Interactions are correct Provider side
- 27. @alexsotob27 We are on Production
- 28. @alexsotob28 Shit! We break Production Environment
- 29. @alexsotob29 Production is not sacrosanct anymore
- 31. Blue/Green Deployment CI/CD PRODUCTION ROUTER USERS BUILD SCM
- 32. Blue/Green Deployment CI/CD PRODUCTION ROUTER USERS BUILDSCM
- 33. Blue/Green Deployment CI/CD PRODUCTION ROUTER USERS SCM
- 34. Blue/Green Deployment CD/CD PRODUCTION ROUTER USERS SCM
- 36. Canary Deployment CI/CD PRODUCTION ROUTER USERS SCM
- 37. Canary Deployment CI/CD PRODUCTION ROUTER USERS SCM
- 38. Canary Deployment CI/CD PRODUCTION ROUTER USERS SCM
- 39. Canary Deployment CI/CD PRODUCTION ROUTER USERS SCM
- 40. Canary Deployment CI/CD PRODUCTION ROUTER USERS SCM
- 41. Canary Deployment CI/CD PRODUCTION ROUTER USERS SCM
- 42. Canary Deployment CI/CD PRODUCTION ROUTER USERS SCM
- 44. Dark Launches DEVELOPMENT QA STAGING PRODUCTION ROUTER USERS SCM INTERNAL USERS
- 45. Shadowing Traffic DEVELOPMENT QA STAGING PRODUCTION ROUTER USERS SCM
- 46. @alexsotob46
- 47. @alexsotob47
- 48. @alexsotob48 As we move to services architectures, we push the complexity to the space between our services CHRISTIAN POSTA
- 49. @alexsotob49 Istio Control Plane Pod Container JVM Service A Envoy Side-car Pod Container JVM Service B Envoy Side-car Pod Container JVM Service C Envoy Side-car HTTP1.1, HTTP2, gRPC, TCP w/TLS HTTP1.1, HTTP2, gRPC, TCP w/TLS HTTP1.1, HTTP2, gRPC, TCP w/TLS Istio Pilot Istio Mixer Istio Auth istioctl, API, config Quota, Telemetry Rate Limiting, ACL CA, SPIFFE Istio Data Plane
- 54. @alexsotob54
- 55. @alexsotob55
- 57. @alexsotob57 Tests are a Team
- 58. @alexsotob58 Testing Evolution to microservices world Manual Tests After Code Automatic Test Test First TDD and BDD Service Virtualization and CDC Testing in Production
- 60. @alexsotob60 Stubbing collaborating services Service A Service B v1 Service B v2 Host:”serviceb-shadow” Service C Service Virtualization X
- 61. @alexsotob61 Synthetic transactions Service A Service B v1 Service B v2 Host:”serviceb-shadow” synthetic:true rollback
- 62. @alexsotob62 Virtualizing test-cluster’s database Service A Service B v1 Service B v2 Host:”serviceb-shadow” Prod DB Virtual DB read Throwaway write
- 63. @alexsotob63 Materializing test-cluster’s database Service A Service B v1 Service B v2 Host:”serviceb-shadow” Prod DB Test DB CDC kafka streams consume CDC
- 65. “Change is the essential process of all of existence.” —SPOCK