Topic: test & qa
Practices in any discipline need continuous review to ensure they are still effective and in line with current requirements. Software testing practices are no exception—the development landscape is highly dynamic, requiring periodic updating of practices. How and when should you review? Read on.
Apple Watch sales are expected to reach more than 36 million units in the first year. As the Apple Watch becomes more of a mainstream product, it is not only expected to bring changes to the user experience but also to software engineering. How will the Apple Watch impact software testing?
We tend to judge based on biases that are a result of our environment, background, culture, and experiences. This is even true for our roles as testers. Here are seven biases that could alter the impartiality in your testing and QA practices. See if you have any inclinations you should correct.
A tester’s productivity and efficiency increasingly is being driven by the set of smart tools used over the course of the testing effort. While all the available options are exciting, the challenge lies in how to go about choosing the right test tools. Commercial or open source? General or niche?
Documenting user requirements is always a challenging phase in software development, as there are no standard processes or notations. However, communication and facilitation skills can make this activity easier. Here are five techniques for converting user stories into testable requirements.
Across disciplines and industries, providing equal accessibility is gradually moving from being “nice to have” to a mandatory aspect of applications. Now is a good time for organizations to start looking at digital accessibility for their products, whether it has been mandated for them yet or not.
When it comes to test design, some people believe in the use of formal test design techniques, while others believe that those same techniques cause rigid thinking and limit creativity. Dale Perry says why formal techniques have value as a basis for formal analysis as well as for creative thinking.
The scope of an accessibility testing effort is very broad—it is often complete only when actual users provide their perspective. Here, a visually impaired user summarizes the accessibility issues he faced in testing an application so that other testers can use this information in their efforts.
The STAREAST testing conference in May featured more than a hundred learning opportunities. Here, we examine the four keynote presentations: Deliberate Testing in an Agile World, The Future of the Software Testing Profession, Blunders in Test Automation, and Innovation: From the Tester’s Viewpoint.
Because accessibility is just starting to really gain awareness in the product development world, organizations are often not fully informed on what it takes to build accessible software—they just want to get there. Here’s a case study from a project that involved making a live product accessible.