Meson/wren
1
0
Fork 0
forked from Mirror/wren
Code Pull Requests Activity
Files
09f4beff4aa572fb5b2e6e035fbfdad501584581
wren/test
History
Bob Nystrom 09f4beff4a Add trim methods on String: 
- trim()
- trim(chars)
- trimEnd()
- trimEnd(chars)
- trimStart()
- trimStart(chars)
2018-07-15 10:48:56 -07:00
..
api
Add test for user data.
2017-03-22 07:26:19 -07:00
benchmark
Add a benchmark for wrenCall().
2015-12-23 17:29:53 -08:00
core
Add trim methods on String:
2018-07-15 10:48:56 -07:00
io
Add Stdin.isTerminal.
2016-05-21 12:51:11 -07:00
language
Move test and tweak code a bit.
2018-04-28 10:08:42 -07:00
limit
Use a map to check for constant collisions.
2016-08-16 07:43:34 -07:00
meta
Tab-completion in REPL based on module variables.
2016-06-09 19:16:41 -07:00
os
Improve Travis Build & Test Coverage
2016-12-29 17:52:38 +00:00
random
Fix test and add skynet example.
2016-02-14 22:21:50 -08:00
regression
Move test and tweak code a bit.
2018-04-28 10:08:42 -07:00
scheduler
"IO" -> "System".
2015-09-15 07:46:09 -07:00
timer
"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.