Re:Commit often, perfect later, publish once: Git best pract...
by phone8675309 on Sunday July 04, 2021 @10:44AM
(#27729982)
A widely used, large framework having really good code coverage is important, especially if not everyone uses all of the framework.
For lots of projects writing some quick end-to-end or story based tests is sufficient, maybe with some randomisation thrown in.
I honestly think the current framework hell we're in has pushed so many hyper-complex best practices that we just waste way too much time on perfecting process over actually coding - tests being one of the paradigms that has gone overboard.