Merge pull request SonarOpenCommunity#1635 from guwirth/test-sq7.5

guwirth · web-flow · commit fbb442e6bcd5 · 2018-12-21T14:08:00.000+01:00
test with SQ 7.5
diff --git a/.travis.yml b/.travis.yml
@@ -13,6 +13,7 @@ env:
         - SONARHOME=/tmp/sonarqube-7.2     SONARAPI=SqApi67
         - SONARHOME=/tmp/sonarqube-7.3     SONARAPI=SqApi67
         - SONARHOME=/tmp/sonarqube-7.4     SONARAPI=SqApi67
+        - SONARHOME=/tmp/sonarqube-7.5     SONARAPI=SqApi75
 
 matrix:
     fast_finish: true
@@ -56,6 +57,8 @@ install:
         - unzip -qq sonarqube-7.3.zip
         - travis_retry wget -q https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-7.4.zip
         - unzip -qq sonarqube-7.4.zip
+        - travis_retry wget -q https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-7.5.zip
+        - unzip -qq sonarqube-7.5.zip
         - travis_retry wget -q https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-3.2.0.1227.zip
         - unzip -qq sonar-scanner-cli-3.2.0.1227.zip
         - travis_retry wget -q https://github.com/htacg/tidy-html5/archive/5.6.0.zip --output-document=tidy-html5.zip
diff --git a/integration-tests/features/importing_clangsa_reports.feature b/integration-tests/features/importing_clangsa_reports.feature
@@ -1,4 +1,4 @@
-@SqApi67
+@SqApi67 @SqApi75
 Feature: Importing Clang Static Analyzer reports
   As a SonarQube user,
   I want to import the Clang Static Analyzer reports into SonarQube.
diff --git a/integration-tests/features/importing_clangsa_scanbuild_reports.feature b/integration-tests/features/importing_clangsa_scanbuild_reports.feature
@@ -1,4 +1,4 @@
-@SqApi67
+@SqApi67 @SqApi75
 Feature: Importing Clang Static Analyzer scan-build reports
 
   As a SonarQube user,
diff --git a/integration-tests/features/importing_coverage.feature b/integration-tests/features/importing_coverage.feature
@@ -3,7 +3,7 @@ Feature: Importing coverage data
   I want to import my coverage metric values into SonarQube
   In order to be able to use relevant SonarQube features
 
-  @SqApi67
+  @SqApi67 @SqApi75
   Scenario: Importing coverage reports
     Given the project "coverage_project"
     When I run sonar-scanner with following options:
@@ -23,7 +23,7 @@ Feature: Importing coverage data
       | line_coverage           | 25.0  |
       | branch_coverage         | 50    |
 
-  @SqApi67
+  @SqApi67 @SqApi75
   Scenario: Zero coverage measures without coverage reports
     If we don't pass coverage reports all coverage measures, except the branch
     ones, should be 'zero'. The branch coverage measures remain 'None'
diff --git a/integration-tests/features/importing_cppcheck_reports.feature b/integration-tests/features/importing_cppcheck_reports.feature
@@ -4,7 +4,7 @@ Feature: Importing Cppcheck reports
   In order to have all static code checking results in one place,
   work with them, filter them etc. and derive metrics from them.
 
-  @SqApi67
+  @SqApi67 @SqApi75
   Scenario: The reports are missing
     Given the project "cppcheck_project"
     When I run "sonar-scanner -X -Dsonar.cxx.cppcheck.reportPath=empty.xml"
@@ -30,7 +30,7 @@ Feature: Importing Cppcheck reports
       """
     And the number of violations fed is 0
 
-  @SqApi67
+  @SqApi67 @SqApi75
   Scenario: The reports use paths relative to directories listed in sonar.sources
     Given the project "cppcheck_project"
     When I run "sonar-scanner -X -Dsonar.cxx.cppcheck.reportPath=relative-to-src.xml"
@@ -43,7 +43,7 @@ Feature: Importing Cppcheck reports
       """
     And the number of violations fed is 0
 
-  @SqApi67
+  @SqApi67 @SqApi75
   Scenario: The reports and issues in the reports have absolute paths
     Given the project "cppcheck_with_absolute_paths_project"
     And platform is not "Windows"
@@ -53,7 +53,7 @@ Feature: Importing Cppcheck reports
     And the server log (if locatable) contains no error/warning messages
     And the number of violations fed is 6
 
-  @SqApi67
+  @SqApi67 @SqApi75
   Scenario Outline: The reports are invalid
     Given the project "cppcheck_project"
     When I run "sonar-scanner -X -Dsonar.cxx.cppcheck.reportPath=<reportpath>"
@@ -70,7 +70,7 @@ Feature: Importing Cppcheck reports
       | unparsable.xml      | 0          |
       | wrongly_encoded.xml | 0          |
 
-  @SqApi67
+  @SqApi67 @SqApi75
   Scenario Outline: Importing Cppcheck reports
     Given the project "cppcheck_project"
     When I run "sonar-scanner -X -Dsonar.cxx.cppcheck.reportPath=<reportpath>"
diff --git a/integration-tests/features/multimodule_analysis.feature b/integration-tests/features/multimodule_analysis.feature
@@ -1,4 +1,4 @@
-@SqApi67
+@SqApi67 @SqApi75
 Feature: cpp-multimodule-project
   Test multimodule project with reports at root of the project
 
diff --git a/integration-tests/features/smoketest.feature b/integration-tests/features/smoketest.feature
@@ -42,3 +42,43 @@ Feature: Smoketest
       | test_failures            | 2     |
       | test_errors              | 0     |
       | tests                    | 4     |
+
+ @SqApi75
+  Scenario: Smoketest
+    Given the project "smoketest_project"
+    When I run "sonar-scanner -X"
+    Then the analysis finishes successfully
+    And the analysis in server has completed
+    And the analysis log contains no error/warning messages except those matching:
+      """
+      .*WARN.*Unable to get a valid mac address, will use a dummy address
+      .*WARN.*cannot find the sources for '#include <gtest/gtest\.h>'
+      .*WARN.*cannot find the sources for '#include <iostream>'
+      .*WARN.*Cannot find the file '.*component_XXX.cc', skipping violations
+      .*WARN.*Cannot find a report for '.*'
+      .*WARN.*Already created edge from 'src/cli/main.cc'.*
+      """
+    And the following metrics have following values:
+      | metric                   | value |
+      | ncloc                    | 56    |
+      | lines                    | 151   |
+      | statements               | 36    |
+      | classes                  | 1     |
+      | files                    | 8     |
+      | directories              | 4     |
+      | functions                | 5     |
+      | comment_lines_density    | 30    |
+      | comment_lines            | 24    |
+      | duplicated_lines_density | 45.7  |
+      | duplicated_lines         | 84    |
+      | duplicated_blocks        | 2     |
+      | duplicated_files         | 2     |
+      | complexity               | 7     |
+      | file_complexity          | 0.9   |
+      | violations               | 12    |
+      | coverage                 | 53.8  |
+      | line_coverage            | 54.8  |
+      | branch_coverage          | 50    |
+      | test_failures            | 2     |
+      | test_errors              | 0     |
+      | tests                    | 4     |
diff --git a/integration-tests/features/test_create_rules_and_bullseye_import.feature b/integration-tests/features/test_create_rules_and_bullseye_import.feature
@@ -1,4 +1,4 @@
-@SqApi67
+@SqApi67 @SqApi75
 Feature: GoogleTestWithBullseyeAndVsProject
   This test verifies that analysis is able to import bullseye coverage reports and import custom rules reports.
   Custom rules are created using Rest API, after test ends rules are deleted.
diff --git a/integration-tests/features/test_execution_statistics.feature b/integration-tests/features/test_execution_statistics.feature
@@ -1,4 +1,4 @@
-@SqApi67
+@SqApi67 @SqApi75
 Feature: Providing test execution numbers
   As a SonarQube user,
   I want to import the test execution reports into SonarQube
diff --git a/integration-tests/features/x_importing_cppcheck_reports_c_cpp.feature b/integration-tests/features/x_importing_cppcheck_reports_c_cpp.feature
@@ -1,4 +1,4 @@
-@SqApi67
+@SqApi67 @SqApi75
 Feature: Importing Cppcheck ANSI-C reports
 
   Scenario Outline: Importing cppcheck issues when c language issues are in report.

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-@SqApi67`
	`1`	`+@SqApi67 @SqApi75`
`2`	`2`	`Feature: Importing Clang Static Analyzer reports`
`3`	`3`	`As a SonarQube user,`
`4`	`4`	`I want to import the Clang Static Analyzer reports into SonarQube.`