aws-sdk-android VS Cypress

Android

This tutorial assumes intermediate React, AWS Amplify, and Node.js knowledge, though you could use the Node.js code with any frontend stack.

There is also an android-specific SDK

AWS provides a range of services that help make setting up an API, database, and email transport quick, and secure. Specifically, AWS Amplify provides a lot of the functionality we'll need out of the box, and Amazon SES will send emails on our behalf.

Now that you have a Next.js app written, you need to get it live online. AWS Amplify supports deploying both SSR and SSG Next.js apps without any additional configuration on your end.

Open source libraries for JavaScript, iOS, Android, and Flutter

Take a look at the official Amplify docs for further information about the framework.

There is AWS Amplify. Take a look at this tutorial. I would caution that the Amplify CLI does a lot of magic that comes with definite downsides if you end up wanting to do more advanced stuff.

We wrote E2E tests with Cypress before Playwright was around and it was awful. The API is weird to the extent that it is basically a DSL based on Javascript. And the tests were flaky because rerenderings could happen between Cypress getting the DOM element and interacting with it. It seems they haven't fixed that one to this day.[0]

The team is also very confident about their approach. They build their own asynchronous concepts that are not interoperable with async/await, openly acknowledge that it is hard to wrap a head around and then dismiss these concerns by asserting that "Asynchronous APIs are here to stay in JavaScript.".[1] The Github issue about the lost DOM elements is also full of answers by a team member intent on writing blog posts that explain what the user is doing wrong rather than fixing the root problem.

I'm really glad that Playwright came around. It is intuitive, pragmatic and has none of the problems above.

[0]: https://github.com/cypress-io/cypress/issues/7306

[1]: https://docs.cypress.io/guides/core-concepts/variables-and-a...

It is so easy to start writing tests with Cypress.io. It seems that Cypress opened doors to testing for everyone with basic JavaScript knowledge. However, when the number of tests grows writing new tests becomes harder. And the issue is not just about writing code. Planning new test scenarios, refactoring, configuring pipelines, and getting test run reports. The more people involved in the product development the more visibility the testing process needs.

if you wanna start out with something simple, I recommend you learn cypress test automation. https://cypress.io has all the documentation you could need, and there are plenty of positions open in NL and elsewhere in Western Europe looking for good test automators.

For Cypress component tests, we already should have cy.stub'd the feature flags. The flags work great with a served app, but in a component or unit test, there is no network call to LD; stubbing the hooks is the way to go. Mind that at the time of writing, because of issue 18552 stubbing modules isn't working in the component runner. The same thing is ok in the e2e runner. In the sample repo this will be updated with Cypress 10.

It's one of common complaints about Cypress - instead of having separate cypress init that generates files once, it will just keep creating boilerplate files if you want them or not.

Cypress 9.5: https://github.com/cypress-io/cypress/releases/tag/v9.5.0

Sounds like cypress.io would be a good fit.

playwrite.dev cypress.io katalon.com testim.io

I am planning to do automation using cypress.io I have already started the project and am currently working on it. Is there any proper way to upload projects in Github? We don't upload the whole project file now, do we?

Cypress 9.4 Release Notes