wren/test at fa8ac84a8b54ce5470fc6365c8f8f90be588636a - wren

mirror of https://github.com/wren-lang/wren.git synced 2026-01-11 22:28:45 +01:00

Files

Bob Nystrom fa8ac84a8b Fix broken test runner (!).

If a test expected an error and found at least one, it would not fail
on any other expected errors that didn't occur.

Also, some tests were expecting a compile time error message even though
the test script doesn't validate those (yet).

The test function was getting monolithic, so I went ahead and split it
into a separate little class.

2015-07-09 08:06:33 -07:00

api

Add API tests for returning null or numbers.

2015-05-24 10:04:24 -07:00

benchmark

Grow the call frame array dynamically.

2015-07-01 00:00:25 -07:00

core

Fix broken test runner (!).

2015-07-09 08:06:33 -07:00

Change IO.read to return null on EOF

2015-03-07 09:10:18 +00:00

language

Fix broken test runner (!).

2015-07-09 08:06:33 -07:00

limit

Fix broken test runner (!).

2015-07-09 08:06:33 -07:00

README.md

This contains the automated validation suite for the VM and built-in libraries.

benchmark/ - Performance tests. These aren't strictly pass/fail, but let us compare performance both against other languages and against previous builds of Wren itself.
core/ - Tests for the built in core library, mainly methods on the core classes. If a bug is in wren_core.c or wren_value.c, it will most likely break one of these tests.
io/ - Tests for the built in IO library. In other words, methods on the IO class. If a bug is in wren_io.c, it should break one of these tests.
language/ - Tests of the language itself, its grammar and runtime semantics. If a bug is in wren_compiler.c or wren_vm.c, it will most likely break one of these tests. This includes tests for the syntax for the literal forms of the core classes.
limit/ - Tests for various hardcoded limits. The language doesn't officially specify these limits, but the Wren implementation has them. These tests ensure that limit behavior is well-defined and tested.