Testing Microservices Techniques for Automation

Size: px

Start display at page:

Download "Testing Microservices Techniques for Automation"

Wendy Nelson
5 years ago
Views:

2 Testing Microservices Techniques for Automation European Testing Conference 2018 Emily

3 Emily Bache Practice Lead for Test Automation Consultant Author of The Coding Dojo

4 Pagero Online Cloud Service Invoice Issuer Invoice Recipient

5 Some numbers We were around 45 developers, in 7 teams We had around 60 microservices Our monolith was in production for nearly 10 years before we started with microservices, 3-4 years ago

6 Pagero Online s architecture

7 A Microservice Provides one business capability Independently Deployable Lightweight API Not too big: fits in my head Docker is used to containerise the service

8 Testing a Microservices Architecture In my experience

9 Test Pyramid: Mike Cohn End-to-End Service Tests Unit End-To-End s exercise the whole system Unit s are for individual functions

10 Testing Strategy for the Monolith Unit s and end-to-end GUI s still valid for Microservices architecture

11 Testing Strategy Testing a monolith Testing a bunch of microservices

12 Testing a Microservice

13 Microservice Tests Deploy your service on localhost (and the database if it has one) Test uses the public API to trigger functionality Mock a response to any calls made to other services or queues Test Case µsut collaborator µs µsdb

14 Faster execution Deploy in Same Process In-process ing: Deploy your service with an in-memory database and in-memory api internal api to set up data and query internals Test Case Internal api µsut collaborator µs µsdb

15 More production-like Out-of-process ing: Deploy your service in one process, and the case in another Security needed for internal api so only /non-production code can access Easier to performance Test Case Deploy in Different Processes µsut collaborator µs µsdb

16 Business-Facing Feature Tests Test a whole scenario across several microservices

17 Testing a whole Feature Test Case This is where it starts getting really complicated

18 Example End-to-End Test Strategy Test crucial workflows, not every detail Use APIs instead of the GUI for most s Techniques: Selective Deployment Keep ing costs as low as possible Approval Testing Event Monitoring

19 Service-layer s in a monolith Test Case A Test Case B Monolith Test cases are for different businessfacing workflows Will exercise different components within the monolith Database

20 Feature s in microservices Test Case A Test Case B Microservices Test cases are for different business-facing workflows Will exercise different groups of microservices Need not deploy everything for every case

21 Selective Deployment Test Case A Need not deploy everything for every case But: all cases needed a few essential infrastructure services.

22 Pagero Online Cloud Service Invoice Issuer Invoice Recipient

23 Parts of a case Invoice Issuer Document Invoice Recipient Test Workflow Recipient Presentation Arrange Act Assert (Almost) all the s involve these elements

24 Approval Testing Invoice Issuer Document Invoice Recipient Test Workflow Recipient Presentation Arrange Act Assert Approval Testing specifies the Assert: compare against an Approved result

25 The Approved Result as Text Recipient Presentation Recipient Presentation in plain text pdf-to-text utility Find the important outputs. Convert them to plain text. Use textual diff to decide if the actual output matches the approved version

26 Elements of a Test Case Invoice Issuer Document Invoice Recipient Test Workflow Recipient Presentation Approved Output Input data varies by case common to many s for reference to determine pass/fail Minimise creation work Minimise maintenance work Maximise serendipity - find bugs you didn t anticipate

27 Debugging a failing? Test Case Which part broke?

28 Correlation ID Pick out all events with 123

29 Event log recorded in a case Helps you to debug what happened when the fails

30 Test Case Elements Invoice Issuer Document Invoice Recipient Test Workflow Event Logs Approved Output Input data varies by case common to many s to debug the to determine pass/fail Recorded traffic is stored with the approved output Recipient Presentation for reference

31 Independent Microservices & Teams Organizing Testing efforts

32 Testing in the pipeline version control unit microservice system manual production Pair Programming, TDD more production-like environment larger pieces of code together Test costs increase monitoring

33 Multi-team development Component B Component A Infrastructure & Architecture Components C&D Components E&F

34 Testing in the pipeline version control unit component system manual production Pair Programming, TDD monitoring

35 Multi-Team CD Team A version control unit microservice system manual production These s are often broken! monitoring Team B

36 Team pipelines Team A version control unit microservice team- system system manual production One environment shared by all teams monitoring Team B

37 Teams Deploy Independently Team A version control unit microservice team- system team- manual incremental roll-out to production monitoring & manual ing Team B

38 Summary Testing in a Microservices Architecture team- system System Tests

39 Summary Testing in a Microservices Architecture team- system System Tests

40 The Continuous Delivery and DevOps Company

UCT Application Development Lifecycle. UCT Business Applications

UCT Application Development Lifecycle. UCT Business Applications UCT Business Applications Page i Table of Contents Planning Phase... 1 Analysis Phase... 2 Design Phase... 3 Implementation Phase... 4 Software Development... 4 Product Testing... 5 Product Implementation...