Unit vs. Integration vs. End-to-End Testing
All three appear as 'testing experience', but they test at different levels and are often done by different people. Unit tests check one small piece of code on its own and are written by developers. Integration tests check that parts work together, such as code and a database. End-to-end tests click through the whole app like a user would and are often owned by QA automation engineers. A developer listing 'testing' usually means unit tests.
How to tell them apart on a resume
Unit testing
JUnit, pytest, Jest, Vitest, mocking, code coverage percentages, TDD — written by developers alongside their own code.
Integration testing
Testcontainers, API tests, contract testing, test databases, Postman/REST Assured — checking services, databases and APIs together.
End-to-end testing
Selenium, Cypress, Playwright, Appium, page objects, flaky tests, CI test suites — usually QA automation or SDET roles.
The question that settles it
“Which kind of tests did you write most — single functions, services working together, or full user journeys through the app — and who owned the others?”
Read the full definitions
Open the full tool for the other look-alike pairs, role profiles, and the JD decoder.