I think these tests are useful as regression tests - unit tests can be really helpful when making changes down the line, tipping you off that you missed something. Also much easier to refactor when there’s good test coverage.

From the PR: unit tests: what are they good for?

Answer: Personal opinion - writing unit testing is not fun. It becomes even less appealing as your codebase grows and maintaining tests becomes a time-consuming chore.

However, the benefits of comprehensive unit tests are real:

Reliability: They create a more reliable codebase where developers can make changes confidently

Speed: Teams can move quickly without fear of breaking existing functionality

Safe Refactoring: Code improvements and restructuring become significantly safer when backed by thorough tests

Living Documentation: Tests serve as clear documentation of your code's behavior:

They show exactly what happens for each input They present changes in a human-readable format: "for this input → expect this output" They run quickly and are easy to execute This immediate feedback loop is beneficial during development