Log in
The cliché always used to be that "contributing to docs was a great way to get started in open source." Now I'm also starting to hear people suggest that writing a test can also be a good entry to a project.
But is this a good idea? I'm not sure...
But not all code and not all tests are created equal.
Is adding a test for a piece of code that is never expected to change in the lifetime of the project valuable?
Is it valuable to write tests for code that is so clearly understandable that if anyone changed it, then lots of things would obviously be wrong, and a manual review of the code would easily spot the problem?
Is it valuable to add tests for only some scenarios or paths through a piece of code? Sometimes. Sometimes not.
Is adding tests that ensure all possible input can be handled by the code a good addition? Maybe, but if the project has been around a while, then all such inputs have likely been encountered already. If there were inputs that might cause a problem, they've most likely been encountered and dealt with.
You may be able to create a lot of tests very quickly. (Especially if using AI.) But is it worth running them? If they don't run quickly, is it worth the delays and the money/energy it takes?
Coded tests must also be reviewed like any other code contribution, and reviewing PRs is a common bottleneck in many OS projects.
I'm not against tests.
I think automated tests are great, and everyone should write more of them.
I just think that adding them after the fact is the wrong time to do it. It's harder to do it well, and they risk being low value.
Writing (or at least documenting) all the required tests before you start coding is the best time to write them.
Writing (or at least documenting) all the required tests before you start coding is the best time to write them.
Of course, if there's a project with documented manual test steps and you want to write code to automate them, then that sounds like a very valuable contribution. (Just as long as it doesn't require modifying the underlying code to make that possible.)
Or, if you want to help with the testing of a project, look at some open issues and start documenting how to test those features when they are implemented.
As with any open source project, the best kind of contributions are the ones the owners and maintainers are asking for, and if they're of any size, they never start with a PR but with a discussion or issue.
