Related Content
 |
Building a Culture of Continuous Improvement A culture of continuous improvement means you are open to improving how you build and deliver. You don't accept the status quo; you choose how to work and feel empowered to change it if it no longer makes sense. Kevin Goldsmith gives some ideas for frameworks to adopt in order to move toward this people-first culture. |
|
 |
4 Impediments to Nurturing a Feedback-Rich Culture Being able to have open, candid conversations that fuel learning, growth, and improvement is critical to a team’s success, so it is important to look out for impediments that can get in the way of having a feedback-rich culture. Here are four common impediments to watch for, as well as behaviors you should nurture. |
|
 |
The Changing Facets of Integration Testing In the current dynamics of product development and confirming quality in the agile world, the definition (both narrow and broad), significance, and scope of integration testing have increased manifold. Rajini Padmanaban highlights the changing facets of integration testing that teams need to make note of. |
|
 |
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. |
|
 |
Is Your Agile Team Taking Every Opportunity for Communication? Scrum events are well-defined points where team members communicate, but they shouldn't be the only times. If you’re not considering coding, tests, and the delivery process as opportunities for a conversation, you are missing an important chance to leverage individuals and interactions, as the Agile Manifesto states. |
|
 |
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. |
