wren/test at 1d1e5d68adbbf052b786bcfe0e771d24e3dab4e8 - wren

Files

T

Bob Nystrom 2dd7578130 feat: add 17 non-crashing regression tests from wren-fuzz for issue #442

These test cases cover malformed class declarations, invalid string literals,
corrupted identifiers, and various edge cases that previously caused crashes
but now produce expected parse errors.

2017-10-08 17:15:15 +00:00

api

feat: add user_data API test and reorder WrenErrorFn vm parameter to first position

2017-03-22 14:26:19 +00:00

benchmark

feat: add wrenGetValueDouble API and benchmark for wrenCall() performance

2015-12-24 01:29:53 +00:00

core

feat: add Num.round method for rounding numbers to nearest integer

2017-10-06 14:51:55 +00:00

feat: add Stdin.isTerminal method to detect TTY connection

2016-05-21 19:51:11 +00:00

language

fix: replace strtol with strtoll for 64-bit hex literal parsing on 32-bit platforms

2017-01-13 05:53:21 +00:00

limit

perf: replace O(n) linear scan with O(1) map lookup for constant deduplication in compiler

2016-08-16 14:43:34 +00: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.