Files
wren/test
Bob Nystrom a6739819b2 Report undefined variable errors on the line where they are used.
This also more importantly ensures the error message for one has a
bounded length even if the variable name is pathologically long.
2016-03-16 08:00:28 -07:00
..
2015-12-23 17:29:53 -08:00
2016-02-27 15:53:02 -08:00
2016-02-19 06:57:38 -08:00
2015-10-15 18:08:56 -07:00
2016-02-14 22:21:50 -08:00
2015-09-15 07:46:09 -07:00
2015-09-15 07:46:09 -07:00
2015-09-15 07:46:09 -07:00

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.