InfoQ Homepage Quality Content on InfoQ
-
/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.
-
/articles/unit-tests-performance-review/en/smallimage/GettyImages-510614905.jpg)
Are Unit Tests Part of Your Team’s Performance Reviews?
No matter how often you conduct performance reviews, there is no doubt unit testing should be one of the metrics measured. Eli Lopian explains what makes a good unit test and how to measure them to ensure your development team is truly agile.
-
/articles/testing-mindset-tools/en/smallimage/logo.jpg)
Enhance Your Testing Skills with Mindset Tools
Quite a lot of testers often miss out on the mindset necessary for the testing and delivery of quality products. Sometimes it seems that quality consciousness is missing. This article is about how I discovered a way to grow my test mindset, and how my discovery has been useful in enhancing my testing skills.
-
/articles/structured-conversations-mvp/en/smallimage/image001.jpg)
Using Structured Conversations to Discover Your MVP
In an increasingly more complex world, finding the smallest possible chunk to deliver to get feedback is essential. This is the idea behind the term MVP. This article describes a model where business and technology together explore the product needs along seven product dimensions, which is a great way of finding small slices of work to develop.
-
/articles/quality-software-factors/en/smallimage/logo.jpg)
Developing Quality Software: Differentiating Factors
The level of software quality attainable is a reflection of an organizational business decision. There are many factors that influence this decision, including development, build and testing environments effectiveness, resources and their associated skillset, integrity, motivations and experience levels, commercial agreements, and adopted processes and productivity tools.
-
/articles/agile-sailors-microservices/en/smallimage/GettyImages-522424397.jpg)
Agile Sailors - A Journey from a Monolithic Approach to Microservices
Over the last couple of years eSailors IT solutions has implemented big technological and organisational changes: from functional silos to cross-functional teams, from a work flow that looked like an assembly line to dynamic loops, from a monolithic platform to microservices, from hierarchical command-and-control to leadership as a team sport. This article provides a summary of their journey.
-
/articles/continuous-delivery-coding-patterns/en/smallimage/logo.jpg)
Continuous Delivery Coding Patterns: Latent-to-Live Code & Forward Compatible Interim Versions
This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.
-
/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/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/0-bugs-policy/en/smallimage/fig0.jpg)
0 Bugs Policy
Gal Zellermayer describes the 0 bugs policy, a process for handling bugs that is based upon 1 rule: whenever you encounter a new bug, you should either fix that bug, or close it as "won't fix" and don't think about it again.
-
/articles/understanding-quality-reliability-qsm/en/smallimage/logo-agile.jpg)
Understanding Quality and Reliability
One of the most overlooked but important areas of software development is quality. It often is not considered or even discussed during the early planning stages of all development projects, but it’s almost always the ultimate criteria for when a product is ready to ship or deploy. This article will explore how to measure quality and minimize the factors that negatively impact software reliability.
-
/articles/no-hotfix-deployment/en/smallimage/logo-agile.jpg)
The Way to No-Hotfix Deployment
Hot-fix redeployment is a waste of time and effort at best, and often a source of further regression, Adam discusses some ready-to-use techniques that helped he and his team reduce the frequency of hot-fix deployments to almost zero.