Download as PDF, PPTX
Uploaded byAlex Soto
Testing in the 21st Century (ExpoQA)
This document discusses testing in the 21st century and provides an overview of modern testing approaches for microservices architectures. It covers principles like service virtualization, contract testing, and canary releases to allow testing systems without relying on external services. Specific tools mentioned include Hoverfly for service virtualization, Pact and contract testing, Istio for traffic routing, and techniques like blue-green deployments, canary releases, and shadowing traffic to safely release updates to production. The presentation emphasizes automating testing and embracing an evolutionary approach to testing practices.
More Related Content
Similar to Testing in the 21st Century (ExpoQA)
Testing in the 21st Century (ExpoQA)
- 1. Testing in the21st Century Alex Soto @alexsotob
- 2. Who Am I? AlexSoto Red Hat Engineer www.lordofthejars.com @alexsotob
- 3.
- 4. Software is eating theworld SOFTWARE IS EATING THE WORLD
- 5. “With great power,there must also come— great responsibility.”
- 8.
- 9. Not talking abouttraditional tests
- 10.
- 11.
- 12.
- 14.
- 15.
- 16.
- 17.
- 18. ServiceVirtualization Capture Mode ServiceA External Network Service B Scripts Proxy
- 19. ServiceVirtualization Simulation Mode ServiceA External Network Service B Scripts Proxy
- 20. hoverctl start hoverctl modecapture curl --proxy http://localhost:8500 http://time.jsontest.com hoverctl mode simulate curl --proxy http://localhost:8500 http://time.jsontest.com Start Hoverfly Proxy Override to use Hoverfly Proxy Stored data
- 21. @Mock EmailService email; Mockito.when(email.receiveBodyMessagesWithSubject("MySubject”)) .thenReturn("This is My Message") // Test calls @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 Record Method Verify Method Called Record Service Verify Service Called
- 22.
- 23. Benefits of SV & Hoverfly •Do not relay on external network • Yet testing all stack • Hoverfly multi-language • Can be used as standalone proxy • Hoverfly JVM • Integration with JVM proxy settings Yet testing all stack trace
- 24.
- 25. Consumer request response Stub Server expectations Provider request response Result DefineConsumer Expectations Verify Expectations On Provider
- 26. @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 Provides predefined Req/Res Executes real requests Consumer side
- 27. @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 Provider side
- 28.
- 29. Benefits of CDC & Pact •Consumer Driven Contracts • Fail fast, independent deployments • Pact Foundation • Pact specification v3 • Integration with Several Languages • JVM, Ruby, Python, Go, .Net, Swift, JS • Pact Broker • Sharing contracts,API documentation, Overview of services
- 30.
- 31. Production is notsacrosanct anymore
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49. As we moveto services architectures, we push the complexity to the space between our services CHRISTIAN POSTA “
- 51. Istio • Greek wordfor “sail” • Fleet configuration • Routing and Load-Balancing control • Observability • ChaosTesting • Security Options
- 52. HTTP1.1, HTTP2, gRPC, TCP w/TLS HTTP1.1, HTTP2,gRPC, TCP w/TLS HTTP1.1, HTTP2, gRPC, TCP w/TLS Pod Containe rJVM Service A Envoy Side-car Pod Containe rJVM Service B Envoy Side-car Pod Containe rJVM Service C Envoy Side-car Istio Pilot Istio Mixer Istio Auth istioctl,API, config Quota,Telemetry Rate Limiting,ACL CA, SPIFFE Istio Data Plane
- 53. New version wasreleased past Friday This contains deprecated format
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60. Stubbing collaborating services ServiceA Service B v1 Service B v2 Host:”serviceb-shadow” Service C Service Virtualization X
- 61. Synthetic transactions Service A ServiceB v1 Service B v2 Host:”serviceb-shadow” synthetic:true rollback
- 62. Virtualizing test-cutter’s database ServiceA Service B v1 Service B v2 Host:”serviceb-shadow” Prod DB Virtual DB read Throwaway write
- 63. Materializing test-cluster’s database ServiceA Service B v1 Service B v2 Host:”serviceb-shadow” Prod DB Test DB CDC kafka streams consume CDC
- 64. Compare live servicetraffic Service B v1’ Service B v2 Host:”serviceb-shadow” Diffy Proxy Service B v1’’ Noise Detection Test
- 65.
- 66. Testing Evolution Manual Tests After Code Automa tic Test Test First TDDand BDD Service Virtualiza tion and CDC Testing in Production
- 67.
- 68. “Change is theessential process of all of existence.” —SPOCK
- 69.