What's this all about?
The goal of the Call Kent Podcast is to get my answers to your questions. You record your brief question (120 seconds or less) right from your browser. Then I listen to it later and give my response, and through the magic of technology (ffmpeg), our question and answer are stitched together and published to the podcast feed.
I look forward to hearing from you!
In 2024, we live in a world where the defacto for creating React applications is SSR (e.g. Remix, react router v7, Next, TanStack). Coupled with the rise in performance, reliability and reduction of cost in running e2e tests by playwright and now vitest's Browser Mode, is it time to consider reworking the Testing Trophy to make e2e tests the largest proportion of the trophy?
This is starting to make more and more sense to me as e2e tests are becoming as cheap to execute as integration tests, whilst integration tests are more complex to write in a SSR application without mocking client side or server side code.
Does the testing trophy need updating for 2025?In 2024, we live in a world where the defacto for creating React applications is SSR (e.g. Remix, react router v7, Next, TanStack). Coupled with the rise in performance, reliability and reduction of cost in running e2e tests by playwright and now vitest's Browser Mode, is it time to consider reworking the Testing Trophy to make e2e tests the largest proportion of the trophy?
This is starting to make more and more sense to me as e2e tests are becoming as cheap to execute as integration tests, whilst integration tests are more complex to write in a SSR application without mocking client side or server side code.
Does the testing trophy need updating for 2025?In 2024, we live in a world where the defacto for creating React applications is SSR (e.g. Remix, react router v7, Next, TanStack). Coupled with the rise in performance, reliability and reduction of cost in running e2e tests by playwright and now vitest's Browser Mode, is it time to consider reworking the Testing Trophy to make e2e tests the largest proportion of the trophy?
This is starting to make more and more sense to me as e2e tests are becoming as cheap to execute as integration tests, whilst integration tests are more complex to write in a SSR application without mocking client side or server side code.
Does the testing trophy need updating for 2025?In 2024, we live in a world where the defacto for creating React applications is SSR (e.g. Remix, react router v7, Next, TanStack). Coupled with the rise in performance, reliability and reduction of cost in running e2e tests by playwright and now vitest's Browser Mode, is it time to consider reworking the Testing Trophy to make e2e tests the largest proportion of the trophy?
This is starting to make more and more sense to me as e2e tests are becoming as cheap to execute as integration tests, whilst integration tests are more complex to write in a SSR application without mocking client side or server side code.
Does the testing trophy need updating for 2025?In 2024, we live in a world where the defacto for creating React applications is SSR (e.g. Remix, react router v7, Next, TanStack). Coupled with the rise in performance, reliability and reduction of cost in running e2e tests by playwright and now vitest's Browser Mode, is it time to consider reworking the Testing Trophy to make e2e tests the largest proportion of the trophy?
This is starting to make more and more sense to me as e2e tests are becoming as cheap to execute as integration tests, whilst integration tests are more complex to write in a SSR application without mocking client side or server side code.
Does the testing trophy need updating for 2025?Have a look at these articles.
