From e8485a24767b844c7ac340dcda3a2ba2e67b0e0c Mon Sep 17 00:00:00 2001
From: Robert Wallach <rowa97@gmail.com>
Date: Wed, 21 Mar 2018 14:27:34 -0500
Subject: [PATCH] Update contract-testing.md

---
 articles/testing/contract-testing.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/articles/testing/contract-testing.md b/articles/testing/contract-testing.md
index 6f3ed76..e025a73 100644
--- a/articles/testing/contract-testing.md
+++ b/articles/testing/contract-testing.md
@@ -28,7 +28,7 @@ Benefits of contract testing include:
 
 ## Connecting a Spec
 
-<!-- FIXME - Show a gif of selecting spec in coverage screen, and clicking on different endpoints -->
+![Connecting a Spec](https://github.com/stoplightio/docs/blob/develop/assets/gifs/contract-test-add-spec.gif?raw=true)
 
 To get started with contract testing, the first thing you will need to do is
 generate a scenario from an OpenAPI specification. To get started:
@@ -69,7 +69,7 @@ You can use the coverage report to quickly stub out a new scenario. To start:
 
 ## Automatic Contract Test Assertion
 
-<!-- FIXME - Show a gif of running a scenario -->
+![Running a Collection](https://github.com/stoplightio/docs/blob/develop/assets/gifs/testing-run-results.gif?raw=true)
 
 After linking your spec to the Scenario Collection, contract test assertions
 will be automatically added as steps within your scenario.