From f5b9a9239cb195d29e201da0fe1f15e994424add Mon Sep 17 00:00:00 2001 From: John Graley Date: Tue, 20 Feb 2024 15:32:22 +0000 Subject: [PATCH] try to fix internal link --- coroutines/docs/testing-with-two-computers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/coroutines/docs/testing-with-two-computers.md b/coroutines/docs/testing-with-two-computers.md index ad7d8afc3..368c32af5 100644 --- a/coroutines/docs/testing-with-two-computers.md +++ b/coroutines/docs/testing-with-two-computers.md @@ -1,7 +1,7 @@ # Testing With Two Computers _This is a simplified overview of conventional and coroutine-based unit testing. We explore the steps taken by a convnetional test and then present the same test in a coroutine model. We use an analogy with computers that can "only do one thing at a time" and then discuss how coroutines fit in at the end._ ## Conventional testing, using one computer -For this exercise, we will assume that the computers illustrated can only run a single "program" at a time (but see [footnote](##Footnote)). +For this exercise, we will assume that the computers illustrated can only run a single "program" at a time (but see [footnote](#Footnote)). ![My test case makes a checklist of events that I will expect during the test.](/coroutines/docs/images/current_1.png) Text after ![I am starting the code-under-test, with an injected dependancy back to me.](/coroutines/docs/images/current_2.png)