What Does It Take to Test in DevOps?: QA Best Practices

Traditionally, testing has been perceived as a bottleneck in SDLC, something that causes delays in delivery. Organizations have long adopted the Agile/DevOps model, but not without its pitfalls and stumbling blocks, especially in achieving the ideal speed/quality balance.

For enterprise DevOps, it is vital to rethink testing approaches to achieve agility at scale. There is much of an overlap of roles, for instance between business analysts and QA testers. Is the tester’s role diminished because of this overlap or because of automation?

Avoid These Common Pitfalls When Transitioning to CI/CD

Avoid these mistakes!

If you have attended an industry event or conference lately, the talk inevitably drifts to development approaches. One thing you hear about a fair amount is the difficulties in the adoption of automated testing, continuous integration, continuous delivery CI/CD pipeline, agile testing, DevOps, test automation, behavior-driven development, and continuous testing among others. While these may sound like buzzwords to the uninitiated, organizations today are adopting many of these approaches successfully to drive faster release cycles along with high-quality software.

What You Need to Know About DevTestOps

What is DevTestOps?

The DevOps movement or culture celebrated its tenth anniversary in 2018. It is now critical to the success of many organizations.

The original definition of DevOps by practitioners Len Bass, Ingo Weber and LIming Zhu is interesting. “It is a set of practices that helps reduce the time between committing a change to a system and committing the change into normal production – all the while ensuring high quality.”