article thumbnail

How To Generate Code Coverage Report Using JaCoCo-Maven Plugin

DZone

Code coverage is a software quality metric commonly used during the development process that let’s you determine the degree of code that has been tested (or executed). To achieve optimal code coverage, it is essential that the test implementation (or test suites) tests a majority percent of the implemented code.

Code 313
article thumbnail

Find vulnerabilities in your code—don’t wait for someone to exploit them

Dynatrace

However, organizations face several challenges with current security testing practices, including: Limited resources: Across the globe, it’s increasingly difficult to find and allocate the necessary personnel to do thorough security testing. High false-positive rates: Traditional security testing tools generate numerous findings.

Code 201
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Fighting Fragility With Property-Based Testing

DZone

Property-based testing (PBT) is such an established technology and it deserves more attention. Java has the Jqwik library, Scala has ScalaCheck and Python has Hypothesis. You encounter some seemingly cutting-edge new tool only to learn it has been around for decades, sometimes inspired by research papers from 1970.

Testing 344
article thumbnail

Unit Testing Log Messages Made Easy

DZone

As a Java Developer, we need to cover a lot of scenarios to ensure the quality of our software and catch bugs as soon as possible when introducing a new code. For 99% of all my use cases AssertJ, Junit, Mockito, and Wiremock are sufficient enough do cover the test cases. So the LogCaptor library came into life.

Testing 360
article thumbnail

Handling Flaky Unit Tests in Java

Uber Engineering

Introduction to Flaky Tests. Unit testing forms the bedrock of any Continuous Integration (CI) system. It warns software engineers of bugs in newly-implemented code and regressions in existing code, before it is merged. It also … The post Handling Flaky Unit Tests in Java appeared first on Uber Engineering Blog.

Java 107
article thumbnail

Optimizing Java XPath CPU and memory overhead by 98%

Dynatrace

This first step clearly shows that the code that powers getFamilyCondition is using a lot of CPU – much more than any other of the top services combined! It can be your own code, 3 rd party code or your runtime that executes for certain tasks such as Garbage Collection. So – we found the culprit!

Java 222
article thumbnail

Unit Testing Console Output Made Easy

DZone

Testing the console output, why even bother? I think any test which asserts some output based on the same action for your target class is useful as it validates the behavior of your service when it is called. Testing these kinds of cases will give you more confidence that your application is working as expected. Introduction.

Testing 269