adieuadieu

Specifically writing some tests with the "Visual comparisons" feature might work.

https://playwright.dev/docs/test-snapshots

De-paywalled link: https://adieuadieu.medium.com/hidden-goodies-in-playwright-t...

De-paywalled link: https://adieuadieu.medium.com/how-to-manage-authentication-s...

De-paywalled link: https://adieuadieu.medium.com/playwright-comes-with-amazing-...

De-paywalled link: https://adieuadieu.medium.com/how-to-write-end-to-end-tests-...

De-paywalled link: https://adieuadieu.medium.com/how-to-use-partiql-with-dynamo...

We're using serverless-chrome for the headless-chrome-on-aws-lambda part. https://github.com/adieuadieu/serverless-chrome

If you're interested in how serverless-chrome works, I wrote an article on how to get headless chrome running on AWS Lambda from scratch here: https://medium.com/@marco.luethy/running-headless-chrome-on-...

For now, we're using the workaround proposed here: https://github.com/adieuadieu/serverless-chrome/issues/41#is...

The Chromeless Proxy service uses the @serverless-chrome/lambda package as is. Same build.

Other than taking a screenshot and evaluating JS code in the context of Chrome and returning JSON, we haven't yet implemented any file-download features. But it might be possible for us to implement something. Would you mind creating an issue here describing your use case so we can discuss it further? https://github.com/graphcool/chromeless/issues/new

;-)

Yep. That's one of the main reasons why we're so excited about this project!

Parallel in that you can invoke many Lambda functions at the same time and have them run independently of each other