coffee/googletest
1
0
Fork 0
mirror of https://github.com/google/googletest.git synced 2025-12-06 16:57:00 +08:00
Code Issues Packages Projects Releases Wiki Activity

trial commit

Browse Source
This commit is contained in:
John Graley 2024-02-20 15:31:44 +00:00 committed by GitHub
parent 2e9e2fad13
commit f41f23aa35
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
coroutines/docs/testing-with-two-computers.md
View File

@ -1,5 +1,7 @@
# Heading # Testing With Two Computers
Text before _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)).
![My test case makes a checklist of events that I will expect during the test.](/coroutines/docs/images/current_1.png) ![My test case makes a checklist of events that I will expect during the test.](/coroutines/docs/images/current_1.png)
Text after Text after
![I am starting the code-under-test, with an injected dependancy back to me.](/coroutines/docs/images/current_2.png) ![I am starting the code-under-test, with an injected dependancy back to me.](/coroutines/docs/images/current_2.png)
@ -9,7 +11,7 @@ Text after
![The call was correct! Now the checklist tells me how to respond to the call.](/coroutines/docs/images/current_4.png) ![The call was correct! Now the checklist tells me how to respond to the call.](/coroutines/docs/images/current_4.png)
Text after Text after
![The code-under-test has completed and I check its output. Test passed!](/coroutines/docs/images/current_5.png) ![The code-under-test has completed and I check its output. Test passed!](/coroutines/docs/images/current_5.png)
Text after ## The same test, using two computers
![I say "please start the code-under-test". I start the code and inject dependency back to me.](/coroutines/docs/images/cotest_1.png) ![I say "please start the code-under-test". I start the code and inject dependency back to me.](/coroutines/docs/images/cotest_1.png)
Text after Text after
![I say "I received this mock call". Inside my test case, I check that the call is correct.](/coroutines/docs/images/cotest_2.png) ![I say "I received this mock call". Inside my test case, I check that the call is correct.](/coroutines/docs/images/cotest_2.png)
@ -18,3 +20,8 @@ Text after
Text after Text after
![I say "the code-under-test has completed and here is its output". I check the output. Test passed!](/coroutines/docs/images/cotest_4.png) ![I say "the code-under-test has completed and here is its output". I check the output. Test passed!](/coroutines/docs/images/cotest_4.png)
Text after Text after
## How do we get to coroutines
## Footnote
The machine shown is a PDP-11/35 minicomputer system which does in fact support timesharing. You would not need two of them to run cotest!