When developers say 'test', why do they only think of unit tests? Why do you think acceptance tests aren’t as common as unit tests despite their impact?
It's only when we become aware of the Modern Test Pyramid https://journal.optivem.com/p/new-test-pyramid that we see the role of Acceptance Tests. It would mean instead of relying on QA Engineers owning E2E Tests, that we would rely on the whole team collaboratively owning Acceptance Tests.
Many developers have only heard of Unit Tests, but not Acceptance Tests. That's why I really seek to make the whole Modern Test Pyramid accessible to developers.
When developers say 'test', why do they only think of unit tests? Why do you think acceptance tests aren’t as common as unit tests despite their impact?
Good question. Generally, when you asking people, they have these associations:
- Developers write Unit Tests and some Integration Tests
- QA Engineers write E2E Tests
I see these associations as coming from the Old Test Pyramid https://journal.optivem.com/p/old-test-pyramid
It's only when we become aware of the Modern Test Pyramid https://journal.optivem.com/p/new-test-pyramid that we see the role of Acceptance Tests. It would mean instead of relying on QA Engineers owning E2E Tests, that we would rely on the whole team collaboratively owning Acceptance Tests.
Many developers have only heard of Unit Tests, but not Acceptance Tests. That's why I really seek to make the whole Modern Test Pyramid accessible to developers.