InfoQ Homepage Software Testing Content on InfoQ
-
/articles/exploring-architecture-building-game/en/smallimage/z-rSFqhA-1650577584417.jpg)
Exploring Architectural Concepts Building a Card Game
One of the things I missed during the pandemic were my friends, the possibility to meet them, discuss with them and, why not, play cards with them. So I decided to implement an app to play Scopone with my friends and, at the same time, test “in the code” some architectural concepts which had been intriguing me for some time.
-
/articles/machine-learning-test-feedback-optimization/en/smallimage/logo-1645210616407.jpg)
Using Machine Learning for Fast Test Feedback to Developers and Test Suite Optimization
Software testing, especially in large scale projects, is a time intensive process. Test suites may be computationally expensive, compete with each other for available hardware, or simply be so large as to cause considerable delay until their results are available. The article explores optimizing test execution, saving machine resources, and reducing feedback time to developers.
-
/articles/remote-ensemble-working-experiment/en/smallimage/logo-1640103875374.jpg)
Remote Ensemble Testing - How an Experiment Shaped the Way We Work
This article shares how an experiment evolved into a common practice at the workplace, using an experimental approach with remote ensemble testing to get teammates on our cross-functional team more involved in the testing activities of the jointly created product. This all started in the times of a global pandemic where the entire team was working from home.
-
/articles/canary-releases-testing/en/smallimage/logo-1635867694318.jpg)
Are Canary Releases an Alternative to Testers?
Canary releases enable product owners to check how a new feature is getting adopted by users by rolling it out to a small percentage of users and then incrementally rolling it out to a wider audience. Product owners might feel tempted to discontinue or reduce testing upon adopting canary releases, but decisions should be approached cautiously as they can have serious and unintended consequences.
-
/articles/session-based-test-management/en/smallimage/test-leadership-applying-session-based-test-management-small-image-1627632157385.jpg)
A Journey in Test Engineering Leadership: Applying Session-Based Test Management
This article shows how modifying Session-based Test Management to our context helped us gain more visibility into our testing. Having a structured yet flexible approach to test management allowed us to make better, more timely decisions about the testing, and gave us more opportunities to influence quality decisions earlier in the process.
-
/articles/series-enhancing-resilience-5/en/smallimage/Resilience-s-1620222675447.jpg)
Continuous Learning as a Tool for Adaptation
The fifth and capstone article in a series on how software companies adapted and continue to adapt to enhance their resilience explores key themes with a special view on the practicality of organizational resilience. It also provides practical guidance to engineering leadership and recommendations on how to create this investment.
-
/articles/2021-state-testing-report/en/smallimage/state-of-testing-2021-small-1620123330431.jpg)
2021 State of Testing Report: Testing Careers, Covid-19, Agile, Coaching & Training, Automation
The 2021 State of Testing report provides insights into the adoption of test techniques, practices, and test automation, and the challenges that testers are facing. Key topics from this report are testing careers, the impact of Covid-19, agile, DevOps and other methodologies, testing coaching & training, and automation and scripting.
-
/articles/reasons-dont-reproduce-remote/en/smallimage/5-reasons-you-shouldnt-reproduce-issues-in-remote-environments-small-1611313980745.jpg)
Five Reasons You Shouldn't Reproduce Issues in Remote Environments
Bugs are an unavoidable part of software development and also one of the biggest time sinks developers face when building software. One way we waste time when working on bugs is trying to reproduce issues in remote test environments. There are some circumstances where this is a wise approach and some where it is a waste. Knowing the difference is an important skill.
-
/articles/cost-coordination-outages/en/smallimage/exploring-costs-of-coordination-during-outages-logo-small-1589968127198.jpg)
Exploring Costs of Coordination During Outages - QCon London Q&A
Coordinating different skills, knowledge and experience is necessary for coping with complex, time-pressured events, but it incurs costs. Well-designed coordination is smooth and can be trained for. Learning how to take initiative, being observable to your counterparts and engaging in reciprocity are examples of strategies engineers can use to lower costs of coordination during outages.
-
/articles/2020-state-testing-report/en/smallimage/state-of-testing-report-2020-s-1588941860947.jpeg)
2020 State of Testing Report
The 2020 State of Testing report provides insights into the adoption of test techniques, practices, and test automation, and the challenges that testers are facing. It shares results from the 2020 testing survey organized by Joel Montvelisky from PractiTest, and Lalit Bhamare from Tea-Time with Testers.
-
/articles/lessons-learned-performance-testing/en/smallimage/lessons-learned-in-performance-testing-logo-small-1574070300297.jpg)
Lessons Learned in Performance Testing
Performance testing is a hard discipline to get right and many things can go wrong. The key is to pay attention to the details, understand the behavior, and avoid just producing fancy numbers. This article describes a few common problems seen frequently with performance testing and shares tips on how to make your performance testing routine better.
-
/articles/microservices-bdd-interface-oriented/en/smallimage/microservices-bdd-interface-oriented-S-1548449537959.jpeg)
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.