Related Content
Predictive Analytics to Give Quality Engineering a Facelift Test automation is only as smart as we design it to be, but automation combined with artificial intelligence and machine learning is what can enable predictive analytics to produce smart outcomes—and that is the facelift quality engineering will soon receive. |
||
A Tester’s Role in Requirements Exploration Agile is supposed to get people to talk to each other in real time. However, many teams still lack a shared understanding of what they are going to build, even as they start coding. As testers, we can explore feature specifications early, contributing to successful and timely delivery through defined requirements. |
||
Improving Requirements with Preemptive Testing Most product defects are created during requirements definition. To significantly reduce and prevent requirements problems, consider making their management your software testers' responsibility. They can identify requirements defects as they are being developed, as well as work out mitigations for their root causes. |
||
The World Has Product Ideas—and So Can You From where do organizations—both big and small—get product ideas? Most often, pioneers and revolution makers have ideas that are homegrown, but today the market is such that the world has ideas. Our industry has plenty of patterns, trends, and ideas to work on and augment. |
||
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. |
||
Mob Programming: Working Well Together Mob programming is a whole-team approach to creating software where everyone works together on the same thing at the same computer. It's not a bunch of people watching one person write code, but rather everyone thinking, discussing, designing, and collaborating. Sound crazy? Here's how it improves the quality of code. |
||
Testing the Requirements: A Guide to Requirements Analysis Everyone knows testing requirements is important, and everyone says they do it, but it seems like no one knows exactly how. The best way to solve this problem is to introduce a requirements analysis stage that has to be done before coding starts. No one knows a product as well as a tester who works with it every day! |
||
Interface Grief: Is It Agile, or Just Bad Software Engineering? There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice? |