Understanding how different testing organizations are setup in enterprise, small product, hyper growth scale up and big tech companies based on my personal experience
Wonderful content. Can you please elaborate on the Test Pyramid approach on these organizations?
In my company, we are like 3rd category. We have a dedicated automation team that takes care of automation. Mostly UI and API. Every release, verifying 3000+ mostly UI cases failures in itself is huge work, span for 3 to 4 days.
Looking for ways to better plan them in future. Your thoughts on how do you follow Test Pyramid would be helpful.
Wonderful content. Can you please elaborate on the Test Pyramid approach on these organizations?
In my company, we are like 3rd category. We have a dedicated automation team that takes care of automation. Mostly UI and API. Every release, verifying 3000+ mostly UI cases failures in itself is huge work, span for 3 to 4 days.
Looking for ways to better plan them in future. Your thoughts on how do you follow Test Pyramid would be helpful.
The only viable way is to encourage devs to write unit and integration tests as part of feature code or refactoring etc,
One way to force this is by doing coverage checks and write linters on CI that block landing the commit if we detect no tests are written or updated.
This way, you are bound to get a better distribution of low level tests than so many E2E tests