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.
Since the start of software development, we have always had to test our software. And over the course of several decades, the discipline of software testing has seen many best practices and patterns developed. Unfortunately however, not all practices have been good and there are also anti-patterns in software testing.
Both Selenium and Cucumber are popular open source test automation frameworks. In this article, Jessica Cyrus explains how to integrate Cucumber and Selenium WebDriver which allows defining automated tests in a language that could be easier to understand outside the software testing team.
When you inherit difficult code it can take weeks to become productive. Having the right tools for software testing and refactoring job and knowing how to use them makes a huge difference. Emily Bache explains this in a series of three posts that deal with approvals and mutation testing; the Lift-Up Conditional refactoring technique; replacing conditional with polymorphism.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates