summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLlewellyn Pritchard <xacc.ide@gmail.com>2024-02-24 01:39:43 +0200
committerGitHub <noreply@github.com>2024-02-24 01:39:43 +0200
commitb1b054ac1bb8477274f68aba9fa9ffda7daea58c (patch)
tree041b5ffeb232a12f44096e2e87703923c710951b
parent794d34fa7927f766488ba3cb4884b07e77300207 (diff)
Update README.md
Some notes about R6RS test suite.
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index 5b8945c2..cb5dcc9d 100644
--- a/README.md
+++ b/README.md
@@ -104,7 +104,9 @@ using IronScheme;
Running tests
=============
-After building, you can use NUnit to run `IronScheme.Tests.dll` in the `IronScheme.Console` bin folder.
+To run the R6RS test suite, call the `(ironscheme-test)` procedure. There are a few known failure cases (currently 3 for .NET desktop). This can be run from the release package as well to confirm IronScheme runs correctly on a new platform or framework.
+
+After building, you can use NUnit to run `IronScheme.Tests.dll` in the `IronScheme.Console` bin folder.
There is also a batch file in the IronScheme directory called `test.cmd`. You can pass the `/verbose` to the batch file to see complete output in case of failures.