Related Content
 |
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. |
|
 |
3 Hidden Benefits of Accessibility Testing Don’t think of implementing accessibility testing just as a way to gain a larger audience for your product (or, worse, just as a way to avoid a lawsuit). There also can be many hidden benefits of complying with accessibility guidelines for you, your site, and your company. Here are three of them. |
|
 |
The Cross-Browser Testing Landscape Is Ready for DevOps While most websites today are responsive, there is a significant growth in progressive web apps that provide cross-platform mobile and web capabilities from within a web app. Add to this maturing practices around agile development and testing and greater adoption of BDD practices, and the landscape is ready for DevOps. |
|
 |
Testing Your DevOps Is Just as Important as Testing Your Software Many DevOps engineers fail to test their automation code in the same way they test the software they deploy. It's crucial for software to have tests, and this should apply to infrastructure-as-code software too, if we plan to change and improve this code with no worries about breaking automation in our DevOps pipeline. |
|
 |
A Definition of Done for DevSecOps In DevOps, we have a software delivery pipeline that checks, deploys, and tests every build. The goal is to produce a viable candidate for production, so we have to look at many different aspects of quality, including security. To be sure we hit all the crucial marks, we should have a definition of done for DevSecOps. |
