You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@phoenix.apache.org by ch...@apache.org on 2020/05/14 07:07:40 UTC

[phoenix] branch 4.x updated: PHOENIX-5892 Add code coverage steps in build documentation

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

chinmayskulkarni pushed a commit to branch 4.x
in repository https://gitbox.apache.org/repos/asf/phoenix.git


The following commit(s) were added to refs/heads/4.x by this push:
     new f21901e  PHOENIX-5892 Add code coverage steps in build documentation
f21901e is described below

commit f21901eaf43ca90189dcc3a5bebcee3250a17f43
Author: Sandeep Guggilam <sg...@sandeepg-ltm.internal.salesforce.com>
AuthorDate: Wed May 13 09:52:39 2020 -0700

    PHOENIX-5892 Add code coverage steps in build documentation
    
    Signed-off-by: Chinmay Kulkarni <ch...@apache.org>
---
 BUILDING.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/BUILDING.md b/BUILDING.md
index 74ea502..8aa8df7 100644
--- a/BUILDING.md
+++ b/BUILDING.md
@@ -73,9 +73,19 @@ Use the m2e eclipse plugin and do Import->Maven Project and just pick the root '
 Running the tests
 -----------------
 
-All tests  
+All Unit tests  
 `$ mvn clean test`
 
+All Unit Tests and Integration tests
+`$ mvn clean verify`
+
+The verify maven target will also run dependency:analyze-only, which checks if the dependencies 
+used in the code and declared in the maven projects match. The code coverage report would be
+generated at /target/site/jacoco/index.html
+
+To skip code coverage analysis
+`$ mvn verify -Dskip.code-coverage`
+
 Findbugs
 --------