wren/test at 33cf8f7b31793e596cced0bc97424787aa58276d - wren - Gitea: Git with a cup of tea

Meson/wren

forked from Mirror/wren

Files

History

Bob Nystrom f47e128978 Tab-completion in REPL based on module variables.

2016-06-09 19:16:41 -07:00

..

Add wrenAbortFiber().

2016-06-09 19:14:21 -07:00

Add a benchmark for wrenCall().

2015-12-23 17:29:53 -08:00

Test that multiple closures of the same code are unequal.

2016-03-26 14:22:38 -07:00

Add Stdin.isTerminal.

2016-05-21 12:51:11 -07:00

Execute input in the REPL.

2016-06-09 19:16:41 -07:00

Error on jump distance overflow.

2016-02-19 06:57:38 -08:00

Tab-completion in REPL based on module variables.

2016-06-09 19:16:41 -07:00

Platform.isWindows.

2016-05-21 12:53:21 -07:00

Fix test and add skynet example.

2016-02-14 22:21:50 -08:00

"IO" -> "System".

2015-09-15 07:46:09 -07:00

"IO" -> "System".

2015-09-15 07:46:09 -07:00

README.md

"IO" -> "System".

2015-09-15 07:46:09 -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.
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.