A feature toggle is a DevOps technique that provides an alternative to maintaining multiple branches in source code, such that a software feature can be tested even before it is completed and ready for release. Feature toggle is used to hide, enable or disable the feature during runtime.
You might think that the crowd testing space is already crowded, but some companies are still expanding like Italian startup AppQuality that announced recently raising €3.5 million in a financial round.
You all know Selenium tests are flaky by nature, slow to run, expensive to maintain and finding the root cause of a failure is not always easy. This presentation shows you how to shift your UI tests left with an Agile testing approach.
You have inherited some legacy C++ code: it is valuable, but it doesn’t have tests, and it wasn’t designed to be testable, so you need to start refactoring. But you can’t refactor safely until the code has tests, and you can’t add tests without refactoring! How can you ever break out of this loop?
Writing and maintaining a suite of acceptance tests that can give you a high level of confidence in the behavior and configuration of your system is a complex task. This presentation describes approaches to acceptance testing that allow teams to work quickly and effectively; build excellent functional coverage for complex enterprise-scale systems; manage and maintain those tests in the face of change, and of evolution in both the codebase and the understanding of the business problem.
Virtual Reality (VR) can be defined as the use of computer technology to create a simulated environment. This technology has a lot of applications in gaming, architecture or training services with specific devices. This article shares some tips on how to perform software testing on virtual reality software.
Every test suite has them: a few tests that usually pass but sometimes mysteriously fail when run on the same code. Since they can’t be reliably replicated, they can be difficult to fix. The good news for software testing is that there is a set of usual suspects that cause these issues: test order, async code, time, sorting and randomness.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates