UI, Unit, Integration, Security Tests required?
My friend Jakob and I are currently developing a finance app:
https://github.com/The-Creative-Programming-Group/finance-io
We’re currently having a discussion regarding testing.
Some of the points mentioned are related to this video by Theo:
https://youtu.be/nSOmL2DxzbU?si=gbt6MJ4wTGPzibii
And also this blog post from PostHog:
https://posthog.com/product-engineers/testing-in-production
The core question is:
Is it meaningful to integrate tests into an app that hasn't been released yet?
My standpoint is:
As soon as we acquire users, we hold a level of responsibility.
Jakob, on the other hand, doesn’t want to add tests. He prefers testing in production.
Why do I believe this approach is problematic?
Especially for a finance app, errors might be detected too late, and could lead to:
Sensitive data being exposed
Financial operations failing or behaving incorrectly
Loss of user trust
Jakob's argument is:
"As long as we don’t have any users, we don’t need tests."
But I believe that releasing version 1.0.0 without tests is risky, since the goal of that version is to:
Start attracting real users
Be used for marketing and outreach
This means the app should already have a baseline of stability and reliability.
He also argues that we should quickly respond to user feedback.
And I agree with that.
But I don't think that contradicts my view. We can still:
Move fast
While having basic automated tests in place to prevent regressions and critical issues
I also believe that an app like this requires:
Planning, defining clear requirements, and
Thinking through features before rushing to ship
This might lead to slightly longer development times, yes.
But it greatly reduces risk and ensures a more secure and higher quality application.
In summary:
Testing early is not about slowing down.
What’s your opinion?
https://github.com/The-Creative-Programming-Group/finance-io
We’re currently having a discussion regarding testing.
Some of the points mentioned are related to this video by Theo:
https://youtu.be/nSOmL2DxzbU?si=gbt6MJ4wTGPzibii
And also this blog post from PostHog:
https://posthog.com/product-engineers/testing-in-production
The core question is:
Is it meaningful to integrate tests into an app that hasn't been released yet?
My standpoint is:
As soon as we acquire users, we hold a level of responsibility.
Jakob, on the other hand, doesn’t want to add tests. He prefers testing in production.
Why do I believe this approach is problematic?
Especially for a finance app, errors might be detected too late, and could lead to:
Sensitive data being exposed
Financial operations failing or behaving incorrectly
Loss of user trust
Jakob's argument is:
"As long as we don’t have any users, we don’t need tests."
But I believe that releasing version 1.0.0 without tests is risky, since the goal of that version is to:
Start attracting real users
Be used for marketing and outreach
This means the app should already have a baseline of stability and reliability.
He also argues that we should quickly respond to user feedback.
And I agree with that.
But I don't think that contradicts my view. We can still:
Move fast
While having basic automated tests in place to prevent regressions and critical issues
I also believe that an app like this requires:
Planning, defining clear requirements, and
Thinking through features before rushing to ship
This might lead to slightly longer development times, yes.
But it greatly reduces risk and ensures a more secure and higher quality application.
In summary:
Testing early is not about slowing down.
What’s your opinion?
GitHub
Contribute to The-Creative-Programming-Group/finance-io development by creating an account on GitHub.
YouTubeTheo - t3․gg
SPONSORED BY POSTHOG
Unit tests, integration tests, staging tests, what about testing in production? Great question. I think we should do it a lot more
Thank you PostHog for sponsoring the video!!! Link to blog post
https://posthog.com/product-engineers/testing-in-production
Check out my Twitch, Twitter, Discord more at https://t3.gg
S/O Ph4...
Unit tests, integration tests, staging tests, what about testing in production? Great question. I think we should do it a lot more
Thank you PostHog for sponsoring the video!!! Link to blog post
https://posthog.com/product-engineers/testing-in-production
Check out my Twitch, Twitter, Discord more at https://t3.gg
S/O Ph4...
At PostHog, we test in production. There are many misconceptions about doing this. It does not mean: we commit to main every time we make a change…
Was this page helpful?
