瀏覽代碼

Unittests are not an absolute hard requirement

Manfred Kröhnert 11 年之前
父節點
當前提交
a22bd6ad3c
共有 1 個文件被更改,包括 1 次插入1 次删除
  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