InfoQ Homepage Testing Content on InfoQ
-
/articles/standardize-requirements-scrum/en/smallimage/logo-agile.jpg)
Standardizing Requirements Descriptions on Scrum Projects for Better Development and Testing Quality
Standardizing requirements descriptions on Scrum projects benefit development and testing quality. Without standardizing, the project may suffer. Standardizing requirements descriptions provides a minimum of eight benefits from requirements descriptions unification, which in turn positively affects testing and makes management of ongoing changes in requirements easier with the help of tools.
-
/articles/technical-hack-conciousness/en/smallimage/logo.jpg)
Technical Practices as a Hack on Consciousness: Why to Hack Yourself
Software technical practices are usually adopted as a means of creating better products. These practices can create and maintain a healthy human system. Technical practices raise the consciousness of individuals and the team as a whole. Technical practices hack consciousness giving us a quick, deep chute into depths of connection that improve our selves, our products, and our world.
-
/articles/book-review-effective-debugging/en/smallimage/cover.jpg)
Q&A with Diomidis Spinellis on Effective Debugging
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.
-
/articles/how-make-agile-successful/en/smallimage/logo.jpg)
So, How Do You Make Agile Successful?
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.
-
/articles/JUnit-5-Early-Test-Drive-Part-2/en/smallimage/java-logo.jpg)
JUnit 5 - An Early Test Drive - Part 2
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.
-
/articles/book-infrastructure-as-code/en/smallimage/logo-devops.jpg)
Book Review and Excerpt: Infrastructure as Code
In this article we review the book Infrastructure as Code - Managing Servers in the Cloud written by Kief Morris, who is leading Continuous Delivery and DevOps at ThoughtWorks Europe. In over 300 pages, Morris lays down the foundation for Infrastructure as Code and outlines the main patterns and practices recommended for building it.
-
/articles/JUnit-5-Early-Test-Drive/en/smallimage/logo.jpg)
JUnit 5 - An Early Test Drive - Part 1
JUnit, Java's most ubiquitous testing framework, is getting an update. Yes, JUnit 5 is a complete rewrite that decouples "JUnit the Platform" from "JUnit the Tool" and makes the platform available to other testing frameworks, which might very well redefine the future of testing on the JVM. More than that, it evolves the API and has a very promising extension model.
-
/articles/building-team-testing-skills/en/smallimage/logo-teamwork.jpg)
Building a Team with Complementary Testing Skills
Imagine meeting with a group to implement a high-level test strategy, then coming back in six months and finding there has been little progress because the director-level executives have been trying to staff projects. I wish I could tell you this was uncommon. Today we'll talk about how the delivery team can acquire all the skills it needs to release software when the number of testers are low.
-
/articles/strategy-handling-defects/en/smallimage/agile-logo.jpg)
Now or Never: the Ultimate Strategy for Handling Defects
How do you handle a long list of defects in your project? You don't. If it is not worth fixing a defect right now, it’s not likely that we will find the time to do it later. Also, it becomes more and more difficult over time to correct the defect, so it is cheaper to solve it now. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them.
-
/articles/performance-tests/en/smallimage/logo.jpg)
Production Like Performance Tests of Web-Services
Tests should always keep the end user view in mind. But how to test web services, which are not directly customer-facing, and in particular, how to performance test them in a meaningful way? This article outlines performance split testing as a performance test approach that is relying on real-time production traffic.
-
/articles/preventing-software-disasters/en/smallimage/logo.jpg)
The Holistic Approach: Preventing Software Disasters
Olivier Bonsignour on what "X-Raying" software means, how it can help prevent software disasters and why CIOs should care.
-
/articles/requirements-traditional-agile-outsourcing/en/smallimage/logo.jpg)
Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"
Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.