added writing tests to your cycle
@@ -4,8 +4,9 @@ Your cycle
1. If you identify something that has to be fixed or done: create an issue. Issues can be associated with projects.
2. If you want to start coding or documenting something, the first step is to check if anyone else is working on this in the list of Pull Requests. If not, create a branch on your local machine, commit something small such as a note or empty file, and push the commit to the same branch on GitHub. Then you can then open a Pull Request. This is for two reasons: you're communicating to the team that you're working on this (so we're not doing things twice), and it gives you and the others an easy way to track your progress.
3. Commit regularly (typically every 10-30 minutes) and give your commits useful messages. "Changes to the data package" does not say anything about what you've done, "Added new feature model" does. If your commit is too large this makes it harder to write a short message.
-4. When you're done with the feature, ask for reviews from two team members or ask the maintainers for help.
-5. When the reviewers have approved the Pull Request, they will merge it into the master branch. At this point you want to checkout the master branch again and pull so that you have your latest changes, and can open a new branch for a new feature.
+4. Write unit-tests to cover your new code. This is easier when you recently wrote the code. Also we require test coverage for your changes to be merged into master!
+5. When you're done with the feature, ask for reviews from two team members or ask the maintainers for help.
+6. When the reviewers have approved the Pull Request, they will merge it into the master branch. At this point you want to checkout the master branch again and pull so that you have your latest changes, and can open a new branch for a new feature.
Rules
