From 830720e3693af4a339407b25077ac01aeaa4f12b Mon Sep 17 00:00:00 2001 From: Robert Wallach Date: Mon, 19 Mar 2018 19:13:26 -0500 Subject: [PATCH] Update contract-testing.md --- articles/testing/contract-testing.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/articles/testing/contract-testing.md b/articles/testing/contract-testing.md index 4d62ac3..379f6a1 100644 --- a/articles/testing/contract-testing.md +++ b/articles/testing/contract-testing.md @@ -54,7 +54,6 @@ You can use the coverage report to quickly stub out a new scenario. To start: 1. Click the **status codes** in the table matrix for the steps you want to add to your scenario. - > Note that the order in which the endpoints are clicked > determines the order in which they will appear in the scenario. For example, @@ -68,8 +67,6 @@ You can use the coverage report to quickly stub out a new scenario. To start: 3. You will automatically be navigated to the new scenario, complete with contract test assertions for each selected endpoint. - - > You will likely need to modify the resulting scenario to fit your use case ## Automatic Contract Test Assertion