DZone

APRIL 6, 2020

You have consistently written unit tests and you have a line coverage of, let us say, 80% and all of your tests pass. Pretty good, isn’t it? But then you change your code and still all of your tests pass although you have changed code which is covered by your unit tests. In this post, we will take a look at mutation testing which will test the quality of your unit tests.

Testing 220

Testing Metrics Code 220

Dynatrace

APRIL 6, 2020

Dynatrace news. New features and enhancements. Easily change OneAgent metadata, host name, and monitoring mode. Java. Added support for Spring AMQP 2.2. Go. Added support for Go 1.14 for Linux, Alpine Linux 64-bit (x86), Windows (x86). Operating systems. Added support for EulerOS 2.3, 2.5, 2.8 (x86). Current support changes. Current OneAgent support changes.

Operating System 103

Operating System Java Technology Technology 103

SQL Shack

APRIL 6, 2020

Table-Valued Parameters aka TVPs are commonly used to pass a table as a parameter into stored procedures or functions. They are helpful in a way, we can use a table as an input to these routines and we can get rid of dealing more complex steps to achieve this process. Introduction Most of us have […].

Servers 68

Servers Processing Performance 68

Nick Desaulniers

APRIL 6, 2020

“War stories” in programming are entertaining tales of truly evil bugs that kept you up at night. Inspired by posts like My Hardest Bug Ever , Debugging an evil Go runtime bug , and others from /r/TalesFromDebugging , I wanted to share with you one of my favorites from recent memory. Recent work. has given me much fulfilment and a long list of truly awful bugs to recount.

C++ 67

C++ Hardware Code Virtualization 67

SQL Performance

APRIL 6, 2020

In the first post in this series , I showed the analysis I used to determine that the default trace is not for us. While looking at what information we actually needed to collect in its place (file size changes), and how this should be exposed to users, I considered the following points about the default trace: it only captures automatic events; it does not capture the "culprit" batch that caused the event, unless you're lucky enough that it was also captured for another reason (e.g.

Servers 61

Servers Tuning Database 61