InfoQ Homepage Testing Content on InfoQ
-
/articles/architecturally-aligned-testing/en/smallimage/logo-1523054954049.jpeg)
Architecturally Aligned Testing
Testing microservices should not be done in a separate test phase, by a dedicated test team, but instead collaboratively by cross-functional teams. There is a shift left in testing to ensure that teams stay autonomous and a shift right in testing towards exploration and experimentation. Continuous Testing and a culture of experimentation are enablers to release microservices fast and reliably.
-
/articles/power-doubt-testing/en/smallimage/logo-int-1521848571570.jpeg)
The Power of Doubt in Software Testing
Being skeptical of ourselves and of what the majority believes keeps us on our toes and forces our mind to work harder. Doubting our own - and other people's - feelings of certainty is a healthy practice that helps us solve problems and avoid bigger problems in the longer run, and it can make us better testers.
-
/articles/microservices-debugging-squash/en/smallimage/logo-apm-1519666054729.jpeg)
Debugging Distributed Systems: Q&A with the “Squash” Microservice Debugger Creator Idit Levine
InfoQ recently sat down with Idit Levine, CEO of solo.io and creator of the new open source “Squash” microservices debugger, and discussed the challenges of observing and debugging distributed systems and applications.
-
/articles/regression-testing-strategies/en/smallimage/Regression-logo-1518799904750.jpg)
Regression Testing Strategies: an Overview
However tedious, regression testing is a powerful gatekeeper protecting product quality. It is present in any project regardless of the development methodology. But how to organize it well? This calls for a quality regression testing strategy that requires good understanding of all aspects of this testing effort (types, methods and approaches). Find out more in our article.
-
/articles/learning-unintended-failures-pattern/en/smallimage/logo-cm-1512460960455.jpeg)
Soft Skill Patterns for Software Developers: The “Learning from Unintended Failures” Pattern
Soft Skill Patterns describe human behaviours that effectively solve recurring problems. The "Learning from Unintended Failures" pattern helps us improve the resilience of a system after a failure. The pattern follows 4 steps: identify a failure, quickly resolve any immediate impact, analyse root cause and system behaviour during the failure, and finally generate and implement improvement ideas.
-
/articles/book-review-what-drives-quality/en/smallimage/logo-book-1509751412232.jpg)
Q&A on the Book What Drives Quality
Quality is a critical aspect of all software products, irrespective of the domain the product is used in and what approach is taken to building it. Ben Linders has released a new book titled "What Drives Quality" in which he provides concrete examples and actionable advice to help identify and improve the quality of software products.
-
/articles/redundant-code/en/smallimage/logo-629286010-small-1506836710190.jpg)
Detecting and Analyzing Redundant Code
As software development projects grow in scope, it is very easy for them to add redundant layers of code. By analyzing several large open source projects on GitHub, the author presents his findings as to the amount of redundant code each project has and shares some recommendations as to how all projects can improve their own code management.
-
/articles/book-review-humans-computers/en/smallimage/book-logo-small.jpg)
Q&A on the Book "Humans vs Computers"
Author Gojko Adzic has released a book, Humans vs Computers, in which he tells stories about the impact of inflexible automation, edge cases and software bugs on the lives of real people. He explains the common mistakes built into the systems and provides advice on how to prevent these mistakes from being built into our systems in the first place.
-
/articles/tdd-ocd/en/smallimage/GettyImages-518897996-copy.jpeg)
Is TDD a Form of OCD?
Developers are increasingly testing their own and each other's code. "Evaluation anxiety" is common psychological condition that is directly impacted by self-testing and team-testing. Are practices like TDD a defense mechanism to protect coders from criticism? And do emerging methods like Behavior Driven Development represents a more emotionally healthy approach to team evaluation?
-
/articles/Microservices-Architectural-Fitness/en/smallimage/logo-java.jpeg)
Perspective on Architectural Fitness of Microservices
In this article we peel the onion of potential architectural fitness of microservices in the context of Master Data Management, and the challenges a microservices-based architecture may face when solving problem domains that require compute-intensive tasks, such as the calculation of expected losses on a portfolio of unsecured consumer credit.
-
/articles/Cascade-Automated-Journey-Testing/en/smallimage/logo-java2.jpeg)
Automated Journey Testing with Cascade
Starting with a brief history of software testing, we investigate Cascade, a new framework for testing “journeys”, eliminating overlapping coverage to produce fast unit tests.
-
/articles/ultimate-feedback-loop/en/smallimage/GettyImages-508140566.jpg)
The Ultimate Feedback Loop: Learning from Customer Reported Defects
Investigating the root causes of customer reported defects will have a great impact on your organization. The best ways to ensure customer satisfaction, lower costs and increase employee engagement is to look inside — you already have the data. At the end, it’s all about continuous improvement.