Scott Feeney

`-p` option doesn't print the source code

4

Hi, I'm getting some weird results with the `-p` option: ``` $ cat foobar.lua print "foobar" $ ./cli.js foobar.lua foobar $ ./cli.js -p foobar.lua [ { index: 0, flags: 2,...

Test more of gentest

4

Using gentest to test itself seems dodgy, so I'm testing it with Mocha right now with explicit calls to `gentest.sample` and assertions about the generated values. I think this is...

In lib/Property.js, there's an interface that could allow people to write their own test runners and use Gentest solely as a library. It implements all the interesting stuff in Gentest...

This could be as simple as saying, "Run gentest --help for a full list of options" in the readme. Worth having at least that.

To make specific test runs reproducible, the `gentest` CLI should print the PRNG seed as part of its output, and allow setting the seed explicitly.

Motivation: the invisible size parameter, which ramps up from 1 to 50 (by default, controllable with `--max-size`) over the course of a test run, controls both array lengths and the...

Currently, Gentest only has a Node.js-based test runner. There should be a bundle you can stick into a script tag to run tests in browsers.

I've been using this command to test sample rate changes: ``` ./luasynth osc -oscType Square -freq 200 -length 10 \ | ./luasynth adsr -attack 30 -decay 500 -sustainLevel -6 -sustainLen...

It wouldn't take much to make the `main.lua` command-line driver work under Windows — same stuff as [this commit for moon-noise](https://github.com/graue/moon-noise/commit/9b45620032b5a8219f4d721571093fb679d63221). A slightly more ambitious goal would be to split...