From 030bc5810b3bef5a873d5a22a32cd807fdc2a83c Mon Sep 17 00:00:00 2001 From: Brittany Johnson Date: Sun, 26 Jan 2020 22:05:14 -0500 Subject: [PATCH] Update README.md --- artifact_documentation/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/artifact_documentation/README.md b/artifact_documentation/README.md index a0a9ba1..af25dda 100644 --- a/artifact_documentation/README.md +++ b/artifact_documentation/README.md @@ -83,7 +83,7 @@ Now let's see how we can use Causal Testing to debug. ## Debugging with Holmes -Holmes is a prototype implementation of our novel testing technique, Causal Testing. Causal Testing conducts causal experiments, which involves perturbing test inputs to find passing executions that are similar to the failing execution, to help developers understand why a given test is failing and how to fix it. +Holmes is a prototype implementation of our novel testing technique, Causal Testing. Causal Testing uses causal experiments, which involves perturbing test inputs to find passing executions that are similar to the failing execution, to help developers understand why a given test is failing and how to fix it. To see how you can use Causal Testing to debug a failing test, we first need to produce the output: