InfoQ Homepage Testing Content on InfoQ
-
The Holistic Approach: Preventing Software Disasters
Olivier Bonsignour on what "X-Raying" software means, how it can help prevent software disasters and why CIOs should care.
-
Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"
Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.
-
Full Stack Testing: Balancing Unit and End-to-End Tests
Full-stack testing can be a widespread and involved task. There are unit tests and end-to-end tests, but how do you know where to focus your efforts? In this article, David Copeland looks at the kinds of tests and how to balance the interplay between those tests and the overall software development effort.
-
Beyond Page Objects: Next Generation Test Automation with Serenity and the Screenplay Pattern
Automated acceptance testing reduces time wasted in manual testing and bug fixing, and when combined with Behaviour-Driven Development, can guide development effort. But it requires skill, practice and discipline. The Screenplay Pattern helps teams address these difficulties and is where you may end up by mercilessly refactoring Page Objects using SOLID design principles.
-
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.
-
Testers in TDD teams
In a team doing TDD (Test Driven Development) there is no need for testers that do manual checking. For testers this means that much of their traditional work disappears. Meanwhile modern testing solutions have become so technical that implementation requires specialists. For testers this presents a very interesting opportunity, but it requires solid technical skills.
-
Agile Approaches in Test Planning
At Agile Testing Days 2015, Eddy Bruin and Ray Oei explained how to satisfy the needs of stakeholders who ask for test cases, test plans, and other comprehensive test artifacts without writing large test plans. An interview about test plans in agile, how to make stakeholders aware that they can influence quality, and which agile practices they recommend for testing.
-
Q&A With Mike Talks on Why Agile Testing Needs Deprogramming
Mike Talks, Test Manager at Datacom, gave a talk at the Agile New Zealand 2015 conference on Deprogramming the Cargo Cult of Testing. Afterwards he explained why agile testing needs deprogramming, and how this can be done.
-
Q&A on the book Leading the Transformation
In the book Leading the Transformation: Applying Agile and DevOps Principles at Scale executives Gary Gruver and Tommy Mouser share their experiences with applying lean and agile development methodologies in enterprise development teams.
-
What’s New in iOS 9: Xcode 7 and Other Developer Tools
In the first four installments of this series, we reviewed new and enhanced frameworks included with iOS 9 SD, changes to Swift and Objective-C, and the new Safari content blocking API. In this article, we will describe what is new within Apple Developer Tools, including Xcode Playgrounds, LLDB, UI testing, Interface Builder, etc.
-
A Conversation with James Shore on Agile Fluency and Let's Code Javascript
At the recent Agile Australia Conference James Shore gave a keynote talk and a workshop on Agile fluency. He spoke to InfoQ about his work on agile fluency, teaching and building tools for test driven development in javascript.
-
Q&A with Ron Jeffries on The Nature of Software Development.
The book "the nature of software development" intents to help people to organize their thoughts about value and find ways to deliver value in software development. It's a book of questions, not of answers, says author Ron Jeffries, for readers to discover the natural way to develop software, the simple way, inside themselves.