We need tests, beyond smoke-tests.
I propose jest everywhere.
One of my goals is to get us to adopt a somewhat test-driven development philosophy for at least the server, and longer-term for the app modules as well. This means that whenever we encounter issues in production, we should—in principle—be addressing them first by creating a failing test to replicate the problem, then writing or fixing code to fix the behavior. Then committing the failing test and the fix together in one commit.
The amount of time this adds to development decreases as we do it more, and it'll make it much easier to validate that everything works as expected once we're done and in the long-term. We just need to commit to it.
We need tests, beyond smoke-tests.
I propose jest everywhere.
One of my goals is to get us to adopt a somewhat test-driven development philosophy for at least the server, and longer-term for the app modules as well. This means that whenever we encounter issues in production, we should—in principle—be addressing them first by creating a failing test to replicate the problem, then writing or fixing code to fix the behavior. Then committing the failing test and the fix together in one commit.
The amount of time this adds to development decreases as we do it more, and it'll make it much easier to validate that everything works as expected once we're done and in the long-term. We just need to commit to it.