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 …

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 …

Jersey has a great possibility to write integration test for REST-APIs, written with Jersey. Just extend the class JerseyTest and go for it. I ran in an issue, where I had to mock a SecurityContext, so that the SecurityContext includes a special UserPrincipal. The challenge is that Jersey wraps the SecurityContext in …

Guest Contribution by Markus Jenderek We wanted to evaluate the new Confluence plugin LivingDoc as a replacement to Fitnesse in order to execute automated web GUI tests. Confluence 5.7.1 (Non-Cloud version) Inside Confluence HSQL In-Memory DB for evaluation purpose LivingDoc plugin 1.0.0.jar Selenium Webdriver for …

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 …