Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Quality Content on InfoQ

  • Kick-off Your Transformation by Imagining It Had Failed

    Large scale change initiatives have a worryingly high failure rate, the chief reason for which is that serious risks are not identified early. One way to create the safety needed for everyone to speak openly about the risks they see is by running a pre-mortem. In a pre-mortem, we assume that the transformation had already failed and walk backward from there to investigate what led to the failure.

  • Q&A on the Book Accelerating Software Quality

    The book Accelerating Software Quality by Eran Kinsbruner explores how we can combine techniques from artificial intelligence and machine learning with a DevOps approach to increase testing effectiveness and deliver higher quality. It provides examples and recommendations for using AI/ML-based solutions in software development and operations.

  • In the Search of Code Quality

    Software development process being a convoluted interplay of technical, business, sociological and psychological forces makes it very hard to understand. This leads to a multitude of myths and hypes. Recent scientific research challenges many commonly held beliefs and intuitions.

  • Learning from Bugs and Testers: Testing Boeing 777 Full Flight Simulators

    The aviation industry has developed the habit of scrutinizing every reported event in order to prevent another occurrence, to understand the root causes and suggest changes to design, process, or better training. This article goes over a couple of noticeable accidents and shows you techniques that could be applied to software development.

  • Q&A on the Book Learning to Scale

    The book Learning to Scale by Régis Medina explores how to apply lean as an education system to scale companies and help people think about their work and learn together to create value. It provides an enterprise model built on how people learn and grow based on the idea that when people understand what they do and why they do it, they become better in what they do and the company moves faster.

  • Q&A on the Book Leading Quality

    The book Leading Quality by Ronald Cummings-John and Owais Peer explores how to become a leader of quality, master strategic quality decisions, and lead engineering/QA teams to accelerate company growth. The book is intended for people who lead quality inside their companies, like C-suite executives.

  • How King uses AI to test Candy Crush Saga

    To be able to improve features in games which are constantly evolving, the challenge will be to scale tests to be on a par with new feature development. Automated tests are vital for King to keep up testing Candy Crush, therefore they are constantly looking for new improved ways to test.

  • 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.

  • 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.

  • Q&A on the Book Refactoring - Second Edition

    The book Refactoring - Second Edition by Martin Fowler explores how you can improve the design and quality of your code in small steps, without changing external behavior. It consists of around seventy detailed descriptions of refactorings, including a motivation for doing them, the mechanics, and an example.

  • 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.