19 Jan How to architect integration or End-to-end(E2E) tests for frontend Single Page Applications(React, Vue, Angular)

Posted at 00:41h in javascript, javascript frameworks, latest, react, testing by
0 Likes
Have you ever had the need to work on Integration or End-to-end (E2E) tests for a Single Page Application made in Javascript that uses a remote backend API? In this blog post, we are going to set up from scratch our Cypress 11 test suite using the Cucumber (Gherkin) syntax and mocking some of those external API requests to ensure stability, reliability, and certainty in our integration tests.
welcome to cypress
In a nutshell, the ETE architecture that we decided to follow for our Single Page Application test suite looks like this:
  • Uses JavaScript as the main language
  • Stubs/mocks/intercepts third-party and external requests
  • Uses the Gherkin syntax (Cucumber)
  • Uses Cypress as the main tool for the End-to-End(e2e) tests and JEST for unit testing.

This time, I decided to collaborate with the company I work for, so you can find the full blog post on that website.

No Comments

Post A Comment