Learnings on Testing & Deployments of UI and BFF in CICD Pipelines for AWS

1

Mochajs

The tradeoff? My integration tests are now run in a Lambda, and you have to do some weirdness to get 'em to work locally via Mocha/Jest, etc. It can work, but NOT traditionally how it's done. It's also not homogeneous in the same test suite setup.

#Development Tools #Javascript UI Libraries #JavaScript Framework 86 social mentions

2

Amazon Route 53

Yes, CloudFront URL's, Route53 on top, or a 3rd party like we use such as CloudFlare can massively impact "well, your code doesn't work when deployed... Thanks for nothing, e2e tests". But that stuff isn't transient much. Once you figure it out, you're good.

#Domain Name Registrar #Cloud Computing #Domain Names 45 social mentions

3

AWS CodeDeploy

#DevOps Tools #Continuous Integration #Continuous Deployment 13 social mentions

4

Amazon CloudFront

Yes, CloudFront URL's, Route53 on top, or a 3rd party like we use such as CloudFlare can massively impact "well, your code doesn't work when deployed... Thanks for nothing, e2e tests". But that stuff isn't transient much. Once you figure it out, you're good.

#CDN #Cloud Computing #Content Distribution 67 social mentions

5

AWS Mobile Services

UI's with Amplify is even stranger. Almost all of us use Cypress where we can. Traditionally this is some Cypress Docker container run in the pipeline, but regular Cypress run locally. With Amplify, they manage the container and they manage the pipeline. However...

#Developer Tools #Realtime Backend / API #App Development 77 social mentions