OSS projects suggesting newbies contribute docs and tests is common, usually only because the author doesn’t want to do it themselves Writing a good test suite or coherent docs is work that requires a huge amount of project context, often much harder than contributing features
-
I’d say contributing tests is way harder than contributing docs. Writing tests is often the hardest part of submitting a PR to an unfamiliar codebase, and I’m more likely to contribute if there’s already a good suite of tests in place that I can use as a reference.
I'm not necessarily recommending it for library owners, but trying to write tests is a good way to learn a library, in the absence of documentation.
-
-
Not a good way but often the only one.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.