From 57e8798ce554f77f5419366e7d88af8e71c59103 Mon Sep 17 00:00:00 2001
From: Remzi Arpaci-Dusseau <remzi.arpacidusseau@gmail.com>
Date: Fri, 29 Mar 2019 07:04:10 -0500
Subject: [PATCH] Quick update to add details on xv6 tests

---
 initial-xv6/README.md | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/initial-xv6/README.md b/initial-xv6/README.md
index 205cb27..a3c3e81 100644
--- a/initial-xv6/README.md
+++ b/initial-xv6/README.md
@@ -59,6 +59,31 @@ Using gdb (the debugger) may be helpful in understanding code, doing code
 traces, and is helpful for later projects too. Get familiar with this fine
 tool!
 
+# Running Tests
+
+Running tests for your system call is easy. Just do the following from
+inside the `initial-xv6` directory:
+
+```sh
+prompt> ./test-getreadcounts.sh
+```
+
+If you implemented things correctly, you should get some notification
+that the tests passed. If not ...
+
+The tests assume that xv6 source code is found in the `src/` subdirectory.
+If it's not there, the script will complain.
+
+The test script does a one-time clean build of your xv6 source code
+using a newly generated makefile called `Makefile.test`. You can use
+this when debugging (assuming you ever make mistakes, that is), e.g.:
+
+```sh
+prompt> make -f Makefile.test qemu-nox
+```
+
+
+