How to Measure Test Coverage in Invoker Tests with JaCoCo
May 31, 2021 · 2 min read · maven test-report integration-testing maven-plugin maven-plugin-testing maven-invoker-plugin jacoco test-coverage ·During the development of the P2 Maven Plugin, I wanted to get an overview about the test coverage of the code. The tests of this plugin can be divided in two groups: Unit tests, that is written with Java, Groovy and JUnit; integration tests, that is written with Maven Invoker Plugin JaCoCo is the defacto standard …
Read MoreTest Coverage Reports For Maven Projects In SonarQube 8.3.x
Jun 10, 2020 · 5 min read · integration-testing jacoco maven sonarqube test-coverage test-report unit-testing ·Some years ago I write a blog post about how to generate test reports in SonarQube separate in test report for unit tests and for integration tests. Since SonarQube 6.2 the test report isn't separate in these categories any more (see SonarQube's blog post). SonarQube merges all test reports to one test report with an …
Read MoreI create a sample Groovy project for Maven, that mixes Spock tests and JUnit 5 tests in one project. In the next section I'll describe how to set up such kind of Maven project. Enable Groovy in the Project First at all, you have to enable Groovy in your project. One possibility is to add the GMavenPlus Plugin to your …
Read MoreThis post demonstrates how JUnit 5 can be used in pre-Java 8 projects and explains why it could be a good idea. JUnit 5 requires at least Java 8 as runtime environment, so you want to update your whole project to Java 8. But sometimes there exists reason why you can't immediately update your project to Java 8. For …
Read MoreThe default setting in Jenkins is to mark a job yellow, when a Maven build fails because of failing tests. If you don't want to have three status of your jobs, you can configure Jenkins so, that the jobs also mark red independent why a Maven build fails. For this you will need administration rights on your Jenkins …
Read MoreUnit And Integration Test Reports For Maven Projects In SonarQube 4.5.1
Jan 30, 2015 · 6 min read · integration-testing jacoco maven sonarqube test-coverage test-report unit-testing ·Since SonarQube 4.2. the test report isn't generated by the Sonar Maven Plugin during a Maven build (see SonarQube's blog post) . Therefore, the test report has to be generated by another plugin before Sonar Maven Plugin collects the information for the SonarQube server. Here, Jacoco Maven Plugin can help. It has the …
Read MoreA new version of this blog post is published under the title "Generate P2 Repository From Maven Artifacts in 2017" Motivation If you use Maven Tycho to build your Eclipse RCP application, you can use Maven dependencies as you know it from Maven (for more information see [1]). I notice that Tycho takes many …
Read MoreThis post describes how to set up a Maven project for a Spring web application with Hessian Service. It also shows how to set up the deployment for exposing the Hessian service and how to set up a client to consume the Hessian service. The Spring Framework version is 3.1.1.RELEASE and the Hessian version is 4.0.7. …
Read MoreThis post describes how to prepare a release for Maven project with a set of Maven Plugins. Background The release preparation phase is built of following common steps: Build the artifact to verify that the build is successful. Run the unit tests of the artifact. Update the version of the artifact to the release …
Read MoreDuring the inspection of several sucessful Maven 3 build output, following SaxException catchs my eye: 1[INFO] Parsing file:/home/skosmalla/.m2/repository/repository.xml 2[Fatal Error] repository.xml:3:1: Premature end of file. 3org.xml.sax.SAXParseException: Premature end of file. 4at …
Read More