[incubator-dubbo.wiki] branch master updated: Updated Test coverage guide (markdown)

[wangxin]

This is an automated email from the ASF dual-hosted git repository.

wangxin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo.wiki.git


The following commit(s) were added to refs/heads/master by this push:
 new 5c2508c  Updated Test coverage guide (markdown)
5c2508c is described below

commit 5c2508cee27a76640d407b91d27301b69125c6f5
Author: Xin Wang 
AuthorDate: Mon Nov 19 22:39:33 2018 +0800

Updated Test coverage guide (markdown)
---
 Test-coverage-guide.md | 15 +--
 1 file changed, 1 insertion(+), 14 deletions(-)

diff --git a/Test-coverage-guide.md b/Test-coverage-guide.md
index 18e9e05..7ca1a59 100644
--- a/Test-coverage-guide.md
+++ b/Test-coverage-guide.md
@@ -1,14 +1 @@
-### 1.The benefits of unit testing 
-  * Unit test code can help everyone to go into details and understand the 
function of the code.
-  * We can find bugs by test case, and then enhance the robustness of the code.
-  * Test case code is also the demo usage of the core code.
-### 2.Some design principle of unit test case 
-  * Steps, fine-grained and combination conditions should be well designed.
-  * Attention to boundary condition test
-  * Test code should also be designed without writing useless code.
-  * When you find a `method` that is hard to write unit test, if you can be 
sure the `method` is "smelly code", then  refactor it with the committer.
-  * The mock framework in dubbo is: [mockito](http://site.mockito.org/). Some 
tutorials:[mockito tutorial](http://www.baeldung.com/bdd-mockito),[mockito 
refcard](https://dzone.com/refcardz/mockito)
-  * TDD（optional）：When you start a new issue, you can try to write test case 
at first 
-### 3.The specified value of the test coverage
-  * In the stage, the test coverage specified value of delta changed codes is 
：>=60%. The higher, the better.
-  * We can see the coverage report in this page: 
https://codecov.io/gh/apache/incubator-dubbo
\ No newline at end of file
+Test coverage guide has bean migrated 
http://dubbo.apache.org/en-us/docs/developers/contributor-guide/test-coverage-guide_dev.html
\ No newline at end of file

[incubator-dubbo.wiki] branch master updated: Updated Test coverage guide (markdown)

[wangxin]

This is an automated email from the ASF dual-hosted git repository.

wangxin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo.wiki.git


The following commit(s) were added to refs/heads/master by this push:
 new 4fde97e  Updated Test coverage guide (markdown)
4fde97e is described below

commit 4fde97ea81bd9d808e6e33cef9a4c86a8d209f5c
Author: Xin Wang 
AuthorDate: Fri Apr 27 11:37:31 2018 +0800

Updated Test coverage guide (markdown)
---
 Test-coverage-guide.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Test-coverage-guide.md b/Test-coverage-guide.md
index 7672f14..74b2f0f 100644
--- a/Test-coverage-guide.md
+++ b/Test-coverage-guide.md
@@ -7,8 +7,8 @@
   * Attention to boundary condition test
   * Test code should also be designed without writing useless code.
   * When you find a `method` that is hard to write unit test, if you can be 
sure the `method` is "smelly code", then  refactor it with the committer.
-  * The mock framework in dubbo is: [mockito](http://site.mockito.org/).
+  * The mock framework in dubbo is: [mockito](http://site.mockito.org/). Some 
tutorials:[mockito tutorial](http://www.baeldung.com/bdd-mockito),[mockito 
refcard])(https://dzone.com/refcardz/mockito)
   * TDD（optional）：When you start a new issue, you can try to write test case 
at first 
 ### 3.The specified value of the test coverage
-  * In the stage, the test coverage specified value of delta changed codes is 
：>=60%
+  * In the stage, the test coverage specified value of delta changed codes is 
：>=60%. The higher, the better.
   * We can see the coverage report in this page: 
https://codecov.io/gh/apache/incubator-dubbo
\ No newline at end of file

-- 
To stop receiving notification emails like this one, please contact
wang...@apache.org.

[incubator-dubbo.wiki] branch master updated: Updated Test coverage guide (markdown)

[wangxin]

This is an automated email from the ASF dual-hosted git repository.

wangxin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo.wiki.git


The following commit(s) were added to refs/heads/master by this push:
 new 72c10a3  Updated Test coverage guide (markdown)
72c10a3 is described below

commit 72c10a3c06cd495d253a4c9882e4a97d61233267
Author: Xin Wang 
AuthorDate: Wed Apr 25 14:32:20 2018 +0800

Updated Test coverage guide (markdown)
---
 Test-coverage-guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Test-coverage-guide.md b/Test-coverage-guide.md
index e73aec2..48f76f2 100644
--- a/Test-coverage-guide.md
+++ b/Test-coverage-guide.md
@@ -7,7 +7,7 @@
   * Attention to boundary condition test
   * Test code should also be designed without writing useless code.
   * When you find a `method` that is hard to write unit test, if you can be 
sure the `method` is "smelly code", then  refactor it with the committer.
-  * The mock framework in dubbo is: [jmockit](http://jmockit.github.io/).
+  * The mock framework in dubbo is: [jmockit](http://jmockit.github.io/) and 
[easymock](http://easymock.org/).
   * TDD（optional）：When you start a new issue, you can try to write test case 
at first 
 ### 3.The specified value of the test coverage
   * In the stage, the test coverage specified value of delta changed codes is 
：>=60%

-- 
To stop receiving notification emails like this one, please contact
wang...@apache.org.

[incubator-dubbo.wiki] branch master updated: Updated Test coverage guide (markdown)

[wangxin]

This is an automated email from the ASF dual-hosted git repository.

wangxin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo.wiki.git


The following commit(s) were added to refs/heads/master by this push:
 new 8155260  Updated Test coverage guide (markdown)
8155260 is described below

commit 8155260f7e51fc797afbb2dc8b51b3cb9fbee241
Author: Xin Wang 
AuthorDate: Wed Apr 25 14:11:43 2018 +0800

Updated Test coverage guide (markdown)
---
 Test-coverage-guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Test-coverage-guide.md b/Test-coverage-guide.md
index abdeaef..e73aec2 100644
--- a/Test-coverage-guide.md
+++ b/Test-coverage-guide.md
@@ -8,7 +8,7 @@
   * Test code should also be designed without writing useless code.
   * When you find a `method` that is hard to write unit test, if you can be 
sure the `method` is "smelly code", then  refactor it with the committer.
   * The mock framework in dubbo is: [jmockit](http://jmockit.github.io/).
-  * TDD（optional）：When you start a new issue, you can try to write test case 
first 
+  * TDD（optional）：When you start a new issue, you can try to write test case 
at first 
 ### 3.The specified value of the test coverage
   * In the stage, the test coverage specified value of delta changed codes is 
：>=60%
   * We can see the coverage report in this page: 
https://codecov.io/gh/apache/incubator-dubbo
\ No newline at end of file

-- 
To stop receiving notification emails like this one, please contact
wang...@apache.org.