wren/test at 33a73ef1d50c32db0cf31559dd3e1cdc46f21ffd - wren

mirror of https://github.com/wren-lang/wren.git synced 2026-01-12 14:48:40 +01:00

Files

Bob Nystrom e8dfb1bf10 Don't test bitwise operations on operands that don't fit in u32.

The current behavior is undefined in C when converting the double to a
u32, so the tests fail on some compilers. For now, I'm just removing
those parts of the tests because I'm not sure what I want the behavior
to be. Modulo? Truncate? Runtime error?

2017-01-12 21:32:50 -08:00

api

Improve Travis Build & Test Coverage

2016-12-29 17:52:38 +00:00

benchmark

Add a benchmark for wrenCall().

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

core

Don't test bitwise operations on operands that don't fit in u32.

2017-01-12 21:32:50 -08:00

Add Stdin.isTerminal.

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

language

Fix assignment test.

2016-10-08 10:51:19 -07:00

limit

Use a map to check for constant collisions.

2016-08-16 07:43:34 -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.