wren/test at 7ed5603ffce7ff86ff6f7050e4921eed89f2f49a - wren

Files

T

Bob Nystrom 7ed5603ffc refactor: rename package module loading to module directory loading in readModule

Rename the internal concept from "package" to "module directory" when loading
module.wren files from subdirectories. Update variable names (packageModule
to moduleDir, packageModulePath to moduleDirPath) and adjust early return
logic to free modulePath before checking contents. Add test for loading
module from a directory and remove old package module test.

2015-03-23 13:48:08 +00:00

benchmark

feat: store precomputed hash in ObjString and use it for equality and hashing

2015-03-18 14:09:03 +00:00

core

feat: add trigonometric methods and Num.pi constant to core library

2015-03-21 19:54:08 +00:00

fix: return null from IO.read on EOF instead of empty string

2015-03-07 09:10:18 +00:00

language

refactor: rename package module loading to module directory loading in readModule

2015-03-23 13:48:08 +00:00

limit

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +00:00

README.md

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +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.
io/ - Tests for the built in IO library. In other words, methods on the IO class. If a bug is in wren_io.c, it should 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.