Related Content
 |
The Test Automation Mindset Building a test automation strategy involves all members of the technical team, layering tests throughout the technology stack, and using this approach to design better software and catch simple problems earlier in the development cycle. But working like that requires a shift in mindset across the organization. |
|
 |
Testing Artificial Intelligence: How Low Can You Go? Artificial intelligence (AI) is propelling to the forefront once more. With the growing importance of AI comes the question: How do I test it? AI systems do not necessarily behave predictably. This means that traditional test cases of the form "do this, expect that" are not always sufficient. |
|
 |
What's in the Summer 2018 Issue of Better Software Magazine For twenty years now, Better Software magazine has published articles offering helpful tips and techniques for those in the software industry. The new issue celebrates those two decades of knowledge-sharing—and, of course, gives you more ideas. Articles this issue focus on leadership and software quality. |
|
 |
Testing the Tester: Building a High-Impact QA Team Teams don’t always understand the impact their roles have on the business outcome, so their lack of focus can affect software quality and lead to an array of disasters. You can help your existing testers become a high-performing QA team focused on goals. Here’s what you can do to transform how your QA team functions. |
|
 |
3 Ways to Keep Your Test Suite Lean Test automation is useful, but as your tests grow, they require maintenance. Without curation, your test suite can turn messy and uncontrollable. Keeping a lean test suite will ensure your tests remain useful. You can whip your test suite into shape by focusing on always making your tests valuable, reliable, and fast. |
|
 |
Automation for the People We tend to contrast automated and manual testing, but really, they should support each other. The key is to define what our testing objectives are, then build the solution needed to achieve them—probably a combination of manual and automated testing. We should not let the method become more important than the results. |
|
 |
Analyzing the Software Team Generalist There's a recent trend in having generalists on the software team—there are no developers or testers, only "team members." The idea of the two roles learning from each other is a good one, but it's usually a one-way street: Testers learn to write production code or test tooling, but no one focuses on deep testing. |
|
 |
Questions to Ask during Test Selection for Automated Tests We use test design techniques to answer the questions “What do I need to test?” and “What tests should I perform?” We try to ensure test coverage during test automation too, except that choosing poorly creates slower builds and unreliable information about product quality. Here are some guidelines for test selection. |
