In the last post, I presented interesting implications of the model of a test case, such as the mathematical object that captures a test’s essence: the core. In this post, I’ll explain how these concepts can help us reduce our testing workload by telling us whether a test does some of the things that another test […]
In the previous post, we explored the model of a test case and showed how we could start seeing when two tests were actually duplicates. But a model is not the entire story. In this post, we will explore a new concept that will guide us closer into the realm of understanding test case duplication. […]
In this post, I continue exploring the vague concept of test case duplication. Eventually, my final goal is to precisely define what we mean in the testing industry by the phrase “duplicate tests.” For that, I’ll cover here a critical concept that will guide our understanding of when test case duplication happens and why it occurs.
How many of these sound familiar to you? “this test is already covered by that other one” “this test is a superset of that one” “these tests seem to cover the same thing” “these two tests are very similar” “this test covers related aspects/functionality as that other test” “these two tests are equivalent” I’ve heard […]
Welcome to another exciting Ortask Progress Webcast! Have you ever run over your allotted testing schedule? Is that a typical thing? Do you get anxious when another test cycle begins? See how the Ortask Scheduling engine can help you!
In this webcast, we share with you a feature we have developed called the test case inference engine of the Ortask client. This webcast was first made available only to members that have signed up.