Okuzeka
Software Engineering vocabulary · Testing

End-to-end test

Meaning in software engineering, with examples

nounCommon term

In software engineering, end-to-end test means: A test that runs a complete user journey through the real system, for example opening the site, logging in and placing an order, to check that everything works together.

In Turkish: uçtan uca test

How it is used

Usually shortened to 'E2E test'. Tools such as Playwright, Cypress and Selenium control a real browser. E2E tests give high confidence but are slow and can be flaky, so teams keep only the most important ones.

Example sentences

  1. Our end-to-end tests cover sign-up, checkout and password reset.

  2. The end-to-end test failed because the email service on staging was down.

Common collocations

  • write end-to-end tests
  • E2E test suite
  • run end-to-end tests
  • end-to-end testing
  • integration testA test that checks how several parts of a system work together, for example your code with a real database or another service.
  • unit testA small automated test that checks one function or class on its own, separate from the database, the network and the rest of the system.
  • flakyDescribing a test that sometimes passes and sometimes fails without any change to the code, often because of timing, the network or shared data.
  • QAShort for quality assurance: the work of checking that software meets its requirements and works well. It also names the people or team who do this work.
  • stagingAn environment set up to be as close as possible to production, where a team checks a release one last time before real users get it.

More terms: Testing

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: