A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
build and run applications without having to manage servers. There are still servers in serverless, but they are abstracted away from app development. Once deployed, serverless apps respond to demand and automatically scale up and down as needed. Serverless offerings from public cloud providers are usually metered on-demand through an event-driven execution model. SERVERLESS - CONCEPT
build and run applications without having to manage servers. There are still servers in serverless, but they are abstracted away from app development. Once deployed, serverless apps respond to demand and automatically scale up and down as needed. Serverless offerings from public cloud providers are usually metered on-demand through an event-driven execution model. SERVERLESS - CONCEPT
build and run applications without having to manage servers. There are still servers in serverless, but they are abstracted away from app development. Once deployed, serverless apps respond to demand and automatically scale up and down as needed. Serverless offerings from public cloud providers are usually metered on-demand through an event-driven execution model. SERVERLESS - CONCEPT
build and run applications without having to manage servers. There are still servers in serverless, but they are abstracted away from app development. Once deployed, serverless apps respond to demand and automatically scale up and down as needed. Serverless offerings from public cloud providers are usually metered on-demand through an event-driven execution model. SERVERLESS - CONCEPT
A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
in data state endpoint request resource state cron job change in data state endpoint request resource state cron job change in data state endpoint request resource state
A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
OBJECT CONTEXT OBJECT function to be executed upon invocation data sent during lambda function invocation methods available to interact with runtime information (request id, log group, etc)
A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
is an open-source framework for building serverless applications It provides shorthand syntax to express functions, APIs, databases, and event source mappings With just a few lines per resource, you can define the application you want and model it using YAML
is an open-source framework for building serverless applications It provides shorthand syntax to express functions, APIs, databases, and event source mappings With just a few lines per resource, you can define the application you want and model it using YAML
is an open-source framework for building serverless applications It provides shorthand syntax to express functions, APIs, databases, and event source mappings With just a few lines per resource, you can define the application you want and model it using YAML
allows to set up a local endpoint that you can use to test your API allows to set up a local endpoint to invoke your local lambda functions start-lambda
A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
tool built for the modern web. It aims to address the pain points developers or QA engineers face while testing an application. Cypress is a more developer-friendly tool that uses a unique DOM manipulation technique and operates directly in the browser.
tool built for the modern web. It aims to address the pain points developers or QA engineers face while testing an application. Cypress is a more developer-friendly tool that uses a unique DOM manipulation technique and operates directly in the browser.
tool built for the modern web. It aims to address the pain points developers or QA engineers face while testing an application. Cypress is a more developer-friendly tool that uses a unique DOM manipulation technique and operates directly in the browser.
A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
browser Retrying tests for a certain time until they succeed or finally fail Easy setup to generate reports Great collection of libraries CYPRESS - STRENGTHS AND DRAWBACKS Embedded HTTP library uses publish - subscribe approach Runs through a browser giving a slow performance The framework was done for E2E UI testing, even it works for other purposes
browser Retrying tests for a certain time until they succeed or finally fail Easy setup to generate reports Great collection of libraries CYPRESS - STRENGTHS AND DRAWBACKS Embedded HTTP library uses publish - subscribe approach Runs through a browser giving a slow performance The framework was done for E2E UI testing, even it works for other purposes
browser Retrying tests for a certain time until they succeed or finally fail Easy setup to generate reports Great collection of libraries CYPRESS - STRENGTHS AND DRAWBACKS Embedded HTTP library uses publish - subscribe approach Runs through a browser giving a slow performance The framework was done for E2E UI testing, even it works for other purposes
browser Retrying tests for a certain time until they succeed or finally fail Easy setup to generate reports Great collection of libraries CYPRESS - STRENGTHS AND DRAWBACKS Embedded HTTP library uses publish - subscribe approach Runs through a browser giving a slow performance The framework was done for E2E UI testing, even it works for other purposes
browser Retrying tests for a certain time until they succeed or finally fail Easy setup to generate reports Great collection of libraries CYPRESS - STRENGTHS AND DRAWBACKS Embedded HTTP library uses publish - subscribe approach Runs through a browser giving a slow performance The framework was done for E2E UI testing, even it works for other purposes
browser Retrying tests for a certain time until they succeed or finally fail Easy setup to generate reports Great collection of libraries CYPRESS - STRENGTHS AND DRAWBACKS Runs through a browser giving a slow performance The framework was done for E2E UI testing, even it works for other
browser Retrying tests for a certain time until they succeed or finally fail Easy setup to generate reports Great collection of libraries CYPRESS - STRENGTHS AND DRAWBACKS Runs through a browser giving a slow performance The framework was done for E2E UI testing, even it works for other purposes
A SERVERLESS FUNCTION 1.4. SERVERLESS APPLICATION MODEL (SAM) 2. TESTING 2.1. WHERE AND WHAT TO TEST A LAMBDA PROJECT 3. CYPRESS 3.1. CONCEPT 3.2. HOW IT WORKS 3.3. STRENGTHS AND DRAWBACKS 3.4. IS A WAY TO GO OR NOT
DEFINITELY NOT NO YES DEFINITELY YES CYPRESS FOR LAMBDA FUNCTIONS TESTING 0 1 2 -1 -2 UNIT TESTING DEFINITELY NOT INTEGRATION TESTING DEFINITELY NOT E2E TESTING YES MANUAL TESTING (HUMAN TRIGGERING) DEFINITELY YES CONTINUOUS INTEGRATION TESTING MAYBE RESULT NO