The book Effective Debugging by Diomidis Spinellis describes 66 different approaches for effective debugging of applications and systems. It provides methods, strategies, techniques, and tools for finding and removing faults, and gives examples for using them in different settings.
It is not Agile's fault, it is your fault - Are you fed up with such statements? This article tries to provide a more constructive answer on how to make Agile successful. It first shows how Scrum can be harmful, then argues how Agile requires different skills on both product and delivery levels. It suggests to use CICD to counteract Scrum's traps and stresses the importance of systems thinking.
JUnit, Java's most ubiquitous testing framework, is getting an update. In part one of our JUnit 5 coverage, we looked at how we got here and wrote some preliminary tests. In part two, we take a closer look at how to run tests and at some of the very cool new features JUnit 5 brings to the table for us developers.
We review the book Infrastructure as Code by Kief Morris, who lays down the foundation for Infrastructure as Code and outlines the main patterns and practices recommended for building it.
JUnit 5 is coming! It thoughtfully improves the JUnit API, has a great extension model, and a revolutionary architecture, which might very well redefine the future of testing on the JVM. 4
Today we'll get tactical, and talk about how the delivery team can acquire all the skills it needs to deliver software when the number of testers are low and specialization is a reality.
How do you handle a long list of defects in your project? You don't. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them. 2
New impetus to performance testing: performance split testing as attempt to make performance testing of web services more dynamic by using real-time production traffic and applying the A/B testing. 3
Olivier Bonsignour on what "X-Raying" software means, how it can help prevent software disasters and why CIOs should care. 3
InfoQ interviewed Suzanne and James Robertson on the "Requirements: The Masterclass LiveLessons - Traditional, Agile, Outsourcing" to get further insights into some of the topics addressed.
The approach to full stack testing can be daunting. There's more than one way to test, but how do you balance your efforts? In this article, David Copeland looks at solving that challenge.
In this article we explore how to create automated fluent BDD scenarios using the Screenplay Pattern – a possible outcome of mercilessly refactoring Page Objects using SOLID design principles. 3