From d38b5f832cb1c032f7727f82ff2e1495193ea66e Mon Sep 17 00:00:00 2001
From: Marshall Lochbaum <mwlochbaum@gmail.com>
Date: Fri, 5 Feb 2021 09:58:49 -0500
Subject: Update information about test cases for VM testing

---
 docs/implementation/vm.html | 6 +++---
 implementation/vm.md        | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/implementation/vm.html b/docs/implementation/vm.html
index b6f563a1..ee665360 100644
--- a/docs/implementation/vm.html
+++ b/docs/implementation/vm.html
@@ -535,8 +535,8 @@
 <p>I recommend roughly the following sequence of tests to get everything working smoothly. It can be very difficult to figure out where in a VM things went wrong, so it's important to work methodically and make sure each component is all right before moving to the next.</p>
 <ul>
 <li>Test core runtime functions directly by calling them within the implementation language.</li>
-<li>Test the virtual machine with small snippets of handwritten bytecode, or with the output of <code><span class='Value'>src</span><span class='Function'>/</span><span class='Value'>cjs.bqn</span></code> on test expressions such as those in <a href="https://github.com/mlochbaum/BQN/blob/master/implementation/../test/bcases.bqn">test/bcases.bqn</a>.</li>
+<li>Test the virtual machine with the output of <code><span class='Value'>src</span><span class='Function'>/</span><span class='Value'>cjs.bqn</span></code> on the primitive-less test expressions in <a href="https://github.com/mlochbaum/BQN/blob/master/implementation/../test/cases/bytecode.bqn">test/cases/bytecode.bqn</a>.</li>
 <li>Now test the self-hosted compiler by running it directly on small expressions.</li>
-<li>For a larger test, use <a href="https://github.com/mlochbaum/BQN/blob/master/implementation/../test/prim.bqn">test/prim.bqn</a>. The result should be an empty list <code><span class='Bracket'>⟨⟩</span></code> indicating no failed tests.</li>
-<li>If test/prim.bqn passes you can almost certainly compile the compiler.</li>
+<li>For a larger test, use <a href="https://github.com/mlochbaum/BQN/blob/master/implementation/../test/cases/prim.bqn">test/cases/prim.bqn</a>. The result should be an empty list <code><span class='Bracket'>⟨⟩</span></code> indicating no failed tests.</li>
+<li>If test/cases/prim.bqn passes you can almost certainly compile the compiler.</li>
 </ul>
diff --git a/implementation/vm.md b/implementation/vm.md
index 3e0c7259..660486d6 100644
--- a/implementation/vm.md
+++ b/implementation/vm.md
@@ -190,7 +190,7 @@ The compiler takes the runtime as `𝕨` and source code as `𝕩`. To evaluate
 I recommend roughly the following sequence of tests to get everything working smoothly. It can be very difficult to figure out where in a VM things went wrong, so it's important to work methodically and make sure each component is all right before moving to the next.
 
 * Test core runtime functions directly by calling them within the implementation language.
-* Test the virtual machine with small snippets of handwritten bytecode, or with the output of `src/cjs.bqn` on test expressions such as those in [test/bcases.bqn](../test/bcases.bqn).
+* Test the virtual machine with the output of `src/cjs.bqn` on the primitive-less test expressions in [test/cases/bytecode.bqn](../test/cases/bytecode.bqn).
 * Now test the self-hosted compiler by running it directly on small expressions.
-* For a larger test, use [test/prim.bqn](../test/prim.bqn). The result should be an empty list `⟨⟩` indicating no failed tests.
-* If test/prim.bqn passes you can almost certainly compile the compiler.
+* For a larger test, use [test/cases/prim.bqn](../test/cases/prim.bqn). The result should be an empty list `⟨⟩` indicating no failed tests.
+* If test/cases/prim.bqn passes you can almost certainly compile the compiler.
-- 
cgit v1.2.3