InfoQ Homepage Testing Content on InfoQ
-
/articles/book-review-testing-digital-age/en/smallimage/testing-in-the-digital-age-logo-1531869927670.jpg)
Q&A on the Book Testing in the Digital Age
The Book Testing in the Digital Age by Tom van de Ven, Rik Marselis, and Humayun Shaukat, explains the impact that developments like robotics, artificial intelligence, internet of things, and big data are having in testing. It explores the challenges and possibilities that the digital age brings us when it comes to testing software systems.
-
/articles/peer-reviews-sandbag-propel/en/smallimage/Peer-Reviews-logo-1531354656439.jpg)
Peer Reviews Either Sandbag or Propel Agile Development
Agile teams are hungry for feedback, but are they getting it fast enough? If your peer review process isn’t structured right, it could be dragging down your development. This article explains how your team can unlock the full potential of code and document reviews by employing a structured, but flexible process that accelerates development and fosters a culture of collaboration
-
/articles/state-of-testing-report-2018/en/smallimage/state-of-testing-1530255125661.jpg)
2018 State of Testing Report
The State of Testing 2018 report provides insights into the adoption of test techniques, practices, and test automation, and the challenges that testers are facing. It shares results from this year’s testing survey. InfoQ held an interview with the organizers of the State of Testing survey.
-
/articles/quick-guide-atdd/en/smallimage/GettyImages-605738830-1525085924100.jpg)
A Quick Guide to Implementing ATDD
Collaboration is one of the core values of Agile Methodology. That being said, what happens when you notice lack of collaboration between developers, testers and business-minded individuals in agile teams? This article provides a quick guide to implementing Acceptance Test Driven Development (ATDD) in your projects to mitigate problems due to lack of collaboration.
-
/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.