Tag: Test Coverage

This post is the second in a 2-part series. As we discussed in my prior post, the Autonomous Software Testing Manifesto, AI provides you, the Automation Engineer, the power to test broadly and deeply across your application. This furnishes you with the opportunity to reevaluate your test strategy and determine what will be most effective

Every day I hear the same question: “how can I improve my coverage with little effort?” Of course, this is a loaded question. What coverage do you mean? There might be (at least) four ways to think about coverage: In the past we defined them this way: So that brings us to modern testing which

We test software so users don’t experience bugs. It follows that all testing should be user centric. This requires intuition and an understanding of design intent when creating tests for new functionality, since users have yet to engage with the new features in a meaningful way. (More on that in a future post.)  Fortunately, the

CI/CD Testing Table Stakes taken Next Level Testing is often ignored when talking about agile, CI/CD and DevOps. And yet, testing is often a major bottleneck in these endeavors. To be successful in any of the above, test must be part of the culture, something done continuously at every build. Ignoring testing in CI/CD is