article thumbnail

Low Code Platforms for Test Automation: A Benchmark

DZone

That also applies to end-to-end automated tests. Considering the trend toward low code solutions for test automation at the UI level, we wanted to run some experiments comparing the execution time of some of the most popular options.

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 319
Insiders

Sign Up for our Newsletter

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

article thumbnail

Measuring Code Quality: Qualitative and Quantitative

DZone

Code Quality defines that the code is good, which means code is of high quality, and code is bad, which means code is of low quality. Code can be considered good quality if it is clear, simple, well tested, bug-free, refactored, documented, and performant.

Code 278
article thumbnail

Testing Even Before a Line of Code Is Written: Is It Possible?

DZone

Testing is often viewed as a necessary evil in software development, in order to ensure the quality of applications. Most commonly, however, testing occurs after the coding process has been completed. In his book, he even wrote that testing should be done “even before a line of code is written.”

Code 246
article thumbnail

Mutation Testing With SonarQube

DZone

In a previous post , we explored the PIT Mutation Testing Maven plugin. Before reading this post, it is advised to revise our previous post about Mutation Testing. In short, with Mutation Testing faults (or mutants) are introduced into your code and consequently, your tests are run again. Introduction.

Testing 340
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

Simple Code: Immutability

DZone

In the world of object-oriented programming, it's not as used and as easy to use approach but there are ways to incorporate immutability to parts of the code and I strongly suggest you do so too. If you're familiar with functional programming you surely recognize the concept of immutability because it's a key ingredient of the paradigm.

Code 264