Slide 1

Slide 1 text

Testing Serverless Applications

Slide 2

Slide 2 text

@slobodan_ Meet Alex

Slide 3

Slide 3 text

@slobodan_ Try serverless! AWS Lambda!

Slide 4

Slide 4 text

@slobodan_ Try serverless! AWS Lambda!

Slide 5

Slide 5 text

@slobodan_

Slide 6

Slide 6 text

@slobodan_

Slide 7

Slide 7 text

@slobodan_ Server

Slide 8

Slide 8 text

@slobodan_ Server OS

Slide 9

Slide 9 text

@slobodan_ Server OS Platform

Slide 10

Slide 10 text

@slobodan_ Server OS Platform App

Slide 11

Slide 11 text

@slobodan_ Server OS Platform App

Slide 12

Slide 12 text

@slobodan_ Server OS Platform App

Slide 13

Slide 13 text

@slobodan_ Server OS Platform App

Slide 14

Slide 14 text

@slobodan_ Server OS Platform App

Slide 15

Slide 15 text

@slobodan_

Slide 16

Slide 16 text

@slobodan_

Slide 17

Slide 17 text

@slobodan_

Slide 18

Slide 18 text

@slobodan_

Slide 19

Slide 19 text

@slobodan_

Slide 20

Slide 20 text

@slobodan_

Slide 21

Slide 21 text

@slobodan_

Slide 22

Slide 22 text

@slobodan_

Slide 23

Slide 23 text

@slobodan_

Slide 24

Slide 24 text

@slobodan_

Slide 25

Slide 25 text

@slobodan_

Slide 26

Slide 26 text

@slobodan_

Slide 27

Slide 27 text

@slobodan_

Slide 28

Slide 28 text

@slobodan_

Slide 29

Slide 29 text

@slobodan_

Slide 30

Slide 30 text

@slobodan_

Slide 31

Slide 31 text

@slobodan_

Slide 32

Slide 32 text

@slobodan_

Slide 33

Slide 33 text

@slobodan_

Slide 34

Slide 34 text

@slobodan_ But how do they fit serverless in their common development process?

Slide 35

Slide 35 text

@slobodan_

Slide 36

Slide 36 text

@slobodan_

Slide 37

Slide 37 text

@slobodan_

Slide 38

Slide 38 text

@slobodan_ Meet Slobodan

Slide 39

Slide 39 text

@slobodan_ Slobodan Stojanovic

Slide 40

Slide 40 text

@slobodan_ Slobodan Stojanovic CTO @ Cloud Horizon and VacationTracker.io

Slide 41

Slide 41 text

@slobodan_ Slobodan Stojanovic CTO @ Cloud Horizon and VacationTracker.io co-author of Serverless Applications with Node.js book

Slide 42

Slide 42 text

@slobodan_ Slobodan Stojanovic CTO @ Cloud Horizon and VacationTracker.io co-author of Serverless Applications with Node.js book AWS Serverless Hero

Slide 43

Slide 43 text

@slobodan_ Slobodan Stojanovic CTO @ Cloud Horizon and VacationTracker.io co-author of Serverless Applications with Node.js book AWS Serverless Hero @slobodan_ effortless-serverless.com

Slide 44

Slide 44 text

@slobodan_ Local testing

Slide 45

Slide 45 text

@slobodan_ Can you run serverless apps locally?

Slide 46

Slide 46 text

@slobodan_ • Azure Functions Core Tools (for Azure functions) • AWS SAM CLI (for AWS SAM) • third-party tools (ie. localstack) • docker-lambda for AWS Lambda local simulation • run Node.js function locally • and more…

Slide 47

Slide 47 text

@slobodan_ But what about permissions or other services, such as AWS Cognito or Kinesis?

Slide 48

Slide 48 text

@slobodan_ You can run parts of your code locally to speed up the development, but not everything

Slide 49

Slide 49 text

@slobodan_ But, even multiple environments per developer are still cheap and (relatively) easy to setup

Slide 50

Slide 50 text

@slobodan_ Can we do better?

Slide 51

Slide 51 text

@slobodan_ Yes, write tests!

Slide 52

Slide 52 text

@slobodan_

Slide 53

Slide 53 text

@slobodan_ Automated testing

Slide 54

Slide 54 text

@slobodan_ Why do we need to test serverless application?

Slide 55

Slide 55 text

@slobodan_ Tools for testing

Slide 56

Slide 56 text

@slobodan_ You can use tools that you are already using

Slide 57

Slide 57 text

@slobodan_ • Jasmine • Mocha • Jest • any other popular tool For example, for Node.js you can use:

Slide 58

Slide 58 text

@slobodan_ What should you test in a serverless app?

Slide 59

Slide 59 text

@slobodan_ Testing pyramid

Slide 60

Slide 60 text

@slobodan_

Slide 61

Slide 61 text

@slobodan_ Testing pyramid vs "Serverless testing pyramid"

Slide 62

Slide 62 text

@slobodan_

Slide 63

Slide 63 text

@slobodan_ Integration tests are cheaper, but also more important, because common serverless app is split into many small pieces

Slide 64

Slide 64 text

@slobodan_ How to write testable function?

Slide 65

Slide 65 text

@slobodan_ • configuration risks • technical workflow risks • business logic risks • integration risks

Slide 66

Slide 66 text

@slobodan_ Hexagonal architecture!

Slide 67

Slide 67 text

@slobodan_ Allow an application to equally be driven by users, programs, automated test or batch scripts, and to be developed and tested in isolation from its eventual run-time devices and databases. Alistair Cockburn

Slide 68

Slide 68 text

@slobodan_

Slide 69

Slide 69 text

@slobodan_

Slide 70

Slide 70 text

@slobodan_ Unit testing

Slide 71

Slide 71 text

@slobodan_ Unit testing is the same as for any other app

Slide 72

Slide 72 text

@slobodan_ • small units • fully covered with tests • "mock" adapters

Slide 73

Slide 73 text

@slobodan_ Integration testing

Slide 74

Slide 74 text

@slobodan_ Integration tests important than ever

Slide 75

Slide 75 text

@slobodan_ • hexagonal architecture • be smart • test integrations that you own • or test your code with a different adapter

Slide 76

Slide 76 text

@slobodan_ How does this look in practice?

Slide 77

Slide 77 text

@slobodan_

Slide 78

Slide 78 text

@slobodan_ UI testing

Slide 79

Slide 79 text

@slobodan_ Serverless is mainly a back end thing, why do we mention UI tests?

Slide 80

Slide 80 text

@slobodan_ UI tests are slow and expensive

Slide 81

Slide 81 text

@slobodan_ Benefits of serverless are cheap infrastructure and easy/fast parallelization

Slide 82

Slide 82 text

@slobodan_

Slide 83

Slide 83 text

@slobodan_ • puppeteer • appraise.qa • and others…

Slide 84

Slide 84 text

@slobodan_

Slide 85

Slide 85 text

@slobodan_ CI / CD

Slide 86

Slide 86 text

@slobodan_ It works the same way as any other app

Slide 87

Slide 87 text

@slobodan_ Use your favorite deployment tool from CI to deploy your serverless app

Slide 88

Slide 88 text

@slobodan_ Popular CI/CD tools

Slide 89

Slide 89 text

@slobodan_ • Jenkins • Travis CI • Semaphore CI • AWS CodeBuild • and many more

Slide 90

Slide 90 text

@slobodan_ We automated deployment from git branches to different stages (ie. production, dev, staging, qa)

Slide 91

Slide 91 text

@slobodan_

Slide 92

Slide 92 text

@slobodan_ Quality Assurance (QA)

Slide 93

Slide 93 text

@slobodan_ Nothing changes?

Slide 94

Slide 94 text

@slobodan_ Stages and deployments are cheap and often fast to setup

Slide 95

Slide 95 text

@slobodan_ You don't pay for your app infrastructure if no-one is using it

Slide 96

Slide 96 text

@slobodan_ Having test environments was never cheaper

Slide 97

Slide 97 text

@slobodan_ Bonus: You can promote tested function to production, so QA tests the same function that will be in production

Slide 98

Slide 98 text

@slobodan_ One more thing…

Slide 99

Slide 99 text

@slobodan_

Slide 100

Slide 100 text

@slobodan_

Slide 101

Slide 101 text

@slobodan_

Slide 102

Slide 102 text

@slobodan_

Slide 103

Slide 103 text

@slobodan_

Slide 104

Slide 104 text

@slobodan_

Slide 105

Slide 105 text

@slobodan_

Slide 106

Slide 106 text

@slobodan_

Slide 107

Slide 107 text

@slobodan_

Slide 108

Slide 108 text

@slobodan_

Slide 109

Slide 109 text

@slobodan_

Slide 110

Slide 110 text

@slobodan_ And they lived happily ever after…

Slide 111

Slide 111 text

@slobodan_

Slide 112

Slide 112 text

@slobodan_

Slide 113

Slide 113 text

@slobodan_ Risks and challenges

Slide 114

Slide 114 text

@slobodan_ Deployment risk

Slide 115

Slide 115 text

@slobodan_ Units are smaller and easier to test, but deployment, triggers and permissions are not trivial (but they are getting easier and easier)

Slide 116

Slide 116 text

@slobodan_ You should use well tested and mature deployment tool

Slide 117

Slide 117 text

@slobodan_ Popular deployment tools

Slide 118

Slide 118 text

@slobodan_ • Serverless Framework • Claudia.js • AWS SAM • .architect • and many more

Slide 119

Slide 119 text

@slobodan_ Integration errors and changes

Slide 120

Slide 120 text

@slobodan_ Your app might just work*, but integrations can change and cause failures

Slide 121

Slide 121 text

@slobodan_ How do you make sure they don't?

Slide 122

Slide 122 text

@slobodan_ You can't. But you should do monitoring and error tracking!

Slide 123

Slide 123 text

@slobodan_ Monitoring/error-tracking tools

Slide 124

Slide 124 text

@slobodan_ • Built-in tools (CloudWatch, X-Ray for AWS) • Epsagon • IOpipe • Dashbird • Thundra • and others

Slide 125

Slide 125 text

@slobodan_ Serverless apps often heavily relies on front end, in those cases you need to track front end errors as well

Slide 126

Slide 126 text

@slobodan_ desole.io

Slide 127

Slide 127 text

@slobodan_

Slide 128

Slide 128 text

@slobodan_

Slide 129

Slide 129 text

@slobodan_

Slide 130

Slide 130 text

@slobodan_

Slide 131

Slide 131 text

@slobodan_ Summary

Slide 132

Slide 132 text

@slobodan_ • you can run/test some parts of serverless app locally • automated tests are important, but be smart • use hexagonal architecture to stay flexible • use CI/CD for tests and deployment to different stages • QA can test the same function you are deploying to production • use mature and tested deployment tools, and track and analyze errors

Slide 133

Slide 133 text

@slobodan_ A few things that I mentioned in the talk: claudiajs.com desole.io

Slide 134

Slide 134 text

@slobodan_ vacationtracker.io

Slide 135

Slide 135 text

@slobodan_ Slides: bit.ly/serverless-testing-btc2018 If you prefer article version: bit.ly/serverless-testing-article

Slide 136

Slide 136 text

@slobodan_ One more thing…

Slide 137

Slide 137 text

@slobodan_ First footage of @slobodan_ and @simalexan as AWS Serverless Heroes Private archive

Slide 138

Slide 138 text

@slobodan_ Serverless Applications with Node.js Use claudia40 promo code for 40% off serverless-book.com @slobodan_

Slide 139

Slide 139 text

@slobodan_ Thank you!

Slide 140

Slide 140 text

@slobodan_ Thank you! Хвала!