Related Content
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. |
||
DevOps and Test Automation: You Missed a Spot The key success factor for DevOps is the commitment from teams, managers, and other stakeholders. There should be agreement that tests and their automation can be important re-usable products, which need attention and cooperation to be able to support approaches like DevOps effectively. |
||
There’s Never Been a Greater Need for Testing You really can’t find the same types of roles that so many testers have occupied for decades, but according to Janet Gregory, an agile testing coach and process consultant with DragonFire, there’s more testing to be done than ever—even if the additional workload they’re being asked to do can be unfair at times. |
||
On Your Software Team, Who Should Own Automation? There is a prevalent question in the software world these days: Who should be working on automation—developers or testers? Justin Rohrman says it can be everyone's responsibility. It’s more important to look at the structure of your technical team, what skill sets are available, and what the skill distribution is. |
||
5 Tips for Balancing Manual and Automated Software Testing Both manual and automated testing are usually necessary to deliver a quality product. We must balance our manual and automated testing activities to achieve both the deployment speed and software quality our customers demand. While there is no one answer for how to do this, here are five tips that can be helpful. |