Blog

Tackling Testing Challenges in an Agile Transition

By Hemanth Yamjala | February 14, 2020

Even though jumping onto the agile bandwagon is tempting for businesses, it is not always easy, and a transition to agile is likely to come with a slew of challenges for testing in particular. In order for agile to enable delivery of quality products at speed, testing has to begin much earlier in the process than ever before. Enabling certain practices will help your organization achieve a more successful transition to agile testing.

The Eroding Agile Test Pyramid

By Wolfgang Platz | February 14, 2020

The test pyramid is a great model for designing your test portfolio. However, the bottom tends to fall out when you shift from progression testing to regression testing. The tests start failing, eroding the number of working unit tests at the base of your pyramid. If you don't have the development resources required for continuous unit test maintenance, there are still things you can do.

The Role of the Test Manager in Agile

By Jeffery Payne | January 24, 2020

In traditional software processes, test managers are responsible for all management aspects of their team. Agile, however, is self-directed, so teams handle all the usual duties. Still, there is a role for test managers in agile, and it’s much more strategic than it was before. Here are the opportunities for the role.

Key Enablers for Continuous Testing

By Raj Subrameyer | January 24, 2020

Continuous testing means testing before, during, and after each software change is made. Testers have long advocated for this, but DevOps has made it more popular by pushing for rapid feedback and shifting testing left in the lifecycle. Here are three practices your company should embrace to enable continuous testing.

6 Reasons Automation Projects Fail

By Raj Subrameyer | January 24, 2020

No matter what the domain or company, there are some common problems that always tend to affect new automation projects. Here are six top reasons automation projects can fail. Keeping these pitfalls in mind will help you to avoid them and instead build stable automation frameworks, making the endeavor a collaborative experience so that your whole team owns automation.