Browse Source

Unittests are not an absolute hard requirement

Manfred Kröhnert 10 years ago
parent
commit
a22bd6ad3c
1 changed files with 1 additions and 1 deletions
  1. 1 1
      CONTRIBUTING.md

+ 1 - 1
CONTRIBUTING.md

@@ -75,7 +75,7 @@ The Amber development model currently revolves around Pull Requests which are cr
 
 
 1. Update to latest Amber master (```git pull```)
 1. Update to latest Amber master (```git pull```)
 2. Develop your feature or bugfix in a local branch (not in ```master```)
 2. Develop your feature or bugfix in a local branch (not in ```master```)
-3. Create unittest for your feature or bugfix (this is required)
+3. Create unittest for your feature or bugfix (your feature/fix will be integrated a lot faster if unittests are present)
 4. Enhance/fix Amber
 4. Enhance/fix Amber
 5. Run the unittests
 5. Run the unittests
 6. Commit your changes to disk if all tests are green
 6. Commit your changes to disk if all tests are green