Blog

blog-banner

Conference Speaker

Paths
By Tom Stiehm | February 14, 2020
Scrum can really help a team to become more agile. But that doesn’t mean it is the only way for a team to become agile. Agile is all about self-organizing teams collaborating to find what works for them, so if a nontraditional approach helps your team get started, then you’re just forging a new path to agility.
blog-banner

Conference Speaker

Human-like robot with artificial intelligence
By Jason Arbon | February 14, 2020
Machine learning is rapidly growing more powerful, already sometimes imitating the actions and judgments of humans better than humans. In the near future, even before machines are conscious, they will be able to mimic human software testers. What will be the impact of AI on testing? Jason Arbon has a bunch of ideas.
blog-banner

Conference Speaker

three cucumbers
By Byron Katz | February 14, 2020
Many people misunderstand the purpose of Cucumber. Because it seems to yield clearer, plain-language test scripts, testers want to use Cucumber as a general-purpose testing tool, including for API tests. But its true purpose is as a BDD framework. You may be thinking, what’s the harm? Here’s why it makes a difference—and why you should choose another tool for API testing.
blog-banner

Hot Topic

Run a usability test
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 image
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.