Related Content
 |
Testing in a Pair Programming Environment If a development team does pair programming, where does testing fit in? You don't have to wait until the programming is done—testers can be part of the whole process, from code design to reviewing changes to production. Pair programming plus a good automation strategy mean quality is built in throughout development. |
|
 |
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? |
|
 |
Continuous Exploratory Testing: Expanding Critical Testing across the Delivery Cycle Continuous testing entails executing automated tests to obtain rapid feedback on business risks. Where does that leave exploratory testing? Obviously, it doesn’t make sense to repeat the same exploratory tests across and beyond a sprint, but exploratory testing can be a continuous part of each software delivery cycle. |
|
 |
Why Smart Testing Requires Strategy and Flexibility You can’t expect to achieve successful testing without the proper strategy, but you also can’t create a strategy that doesn’t allow you to adapt along the way. Think about why you’re testing, and be confident enough to change course if you feel it can benefit your team and project. |
|
 |
Using Feature Flags to Boost Testing and Deployment A feature flag is a configuration setting that lets you turn a given feature on or off. There is no need for a feature to be complete before you can start testing—as soon as the first piece of code is merged, you can turn the flag on in your test environment and begin. This also reduces risk. Do you use feature flags? |
|
 |
What We Talk about When We Talk about Test Automation Testers talking about test automation often mean browser automation. Developers are probably talking about unit testing or something at the service layer. And operations people are most likely thinking of monitoring and the guts that control continuous integration. But the practices are more important than terminology. |
|
 |
The Role of Testers on Agile Teams Some agile teams have so fully embraced the idea of the development team owning quality that they don't hire anyone with a testing background, instead making software engineers responsible for all phases of quality. Still, testers add value to a team in many ways that don’t involve test execution. Where do they fit in? |
|
 |
Test Automation Cannot Be an Afterthought In software testing, automation can be viewed as an editor, of sorts. Previously, manual testers had to be extremely thorough to guarantee quality since they were the final check before products got into the hands of users. Now, testers can lean on automation tools to catch any bugs that might have been missed. |
