Re:How ‘open’ should your open source be?
by josephg on Sunday May 14, 2023 @10:32AM
(#35938301)
Yep. I have a strict policy of requiring unit tests to be added before I merge any new feature in a pull request. For small features, all the contributor needs to do is add a couple of test functions to the existing testing infrastructure, but I find it still drops the number of PRs by about 5x or something. It’s really remarkable. And I haven’t found a downside to this policy yet.
[ Parent
| on HN ]
Re:How ‘open’ should your open source be?
by MoreQARespect on Sunday May 14, 2023 @10:52AM
(#35938449)
I have this too, but with a specification-by-example integration test with a brief explanation that autogenerates readable "step by step" markdown how-to docs.
The idea being that new features should be fully tested and clearly documented before being merged - ideally with a minimum of overhead. Because if you defer either, it likely won't get done.