InfoQ Homepage Testing Content on InfoQ
-
Test-Driven Development: Really, It’s a Design Technique
Using a step-by-step example in Java, this article provides a practical example of how to use test-driven development (TDD) to divide, test, and conquer larger problems when coding.
-
Test Automation: Prevention or Cure?
A lot of teams have the tendency to view test automation as a way of speeding up delivery of software, as this is often the perceived bottleneck within the team, but if they were to take a deeper look at their development practices as a whole, they may get better results.
-
Service Virtualization Meets Java: Hoverfly Tutorial
Service virtualization is a technique used to simulate the behavior of dependencies of service during automated testing. This article explores this topic, and includes a tutorial using Hoverfly Java.
-
Bots Are Coming! Approaches for Testing Conversational Interfaces
Voice-based computing interfaces need testing with an adapted approached, suited for their specificity and context. Some things need to be adapted (test strategy, testing approach, validation criteria), while others can be re-used (e.g. API testing approaches and tools), and some require learning new things (e.g. testing artificial intelligence models and components).
-
Tap Compare Testing with Diferencia and Java Microservices
“Tap compare” is a testing technique that allows you to test the behavior and performance of the new service by comparing its results against the old service. This article provides an example of using a new open source tool, Diferencia, and mirroring production traffic across both old and new services to compare the difference in result.
-
Who is in Charge of Quality in Software Development
As silos break down, the whole team is responsible for quality in software development. As process more and more defines people and processes, how can you strive for better quality of releases?
-
Test Automation in the World of AI & ML
An in-depth look at the criteria & requirements for Functional Test Automation in the agile world, and the capabilities you should build in your custom framework, or should exist the tools you choose. Anand Bagmar explores aspects like readability, reuse, debugging / rca, CI, Test Data, Parallel Execution, integration with other tools & libraries, free Vs open-source and support.
-
Developing Microservices with Behavior Driven Development and Interface Oriented Design
These dependencies require well-defined and well-tested services. Behavior Driven Development (BDD) and Interface Oriented Design (IOD) help achieve this. BDD concentrates on the functionality of the services, which are specified with tests. IOD identifies contractual obligations (e.g. failure reporting) of the services.
-
How to Slow Down to Go Faster Than Ever in Software Development
Going fast without control could be the biggest enemy of software development. By slowing down on people, we improve professionalism and craftsmanship. By slowing down on process, we improve adaptation and efficiency. And by slowing down on product, we improve automation and quality. When we focus on these areas, we start to cultivate a development culture enabling software development fast.
-
The 2018 InfoQ Editors’ Recommended Reading List: Part Two
As part of our core values of sharing knowledge, the InfoQ editors were keen to capture and share our book and article recommendations for 2018, so that others can benefit from this too. In this second part we are sharing the final batch of recommendations
-
James Bach on a Career in Testing and Advice for New Players
In this interview, James Bach explores making software testing legible and how to assess the values of your testing work and risk in a software product. He talks about how to overcome the testing automation pesticide paradox, and how should we leverage AI and ML in our testing. With more than 30 years software testing experience, Bach gives three pieces of advice to software testing beginners.
-
Adopting Continuous Delivery at teamplay, Siemens Healthineers
Continuous Delivery is about working in a way that keeps the system in a releasable state throughout its development. This article describes how a large software development organization at Siemens Healthineers started the transformation towards Continuous Delivery. It describes the strategy and tactics used to gradually and safely change the development process in a regulated medical domain.