Add unit tests

[joelmccracken]

It seems like this could be extremely useful.

A decent project to start with might be bats: https://github.com/sstephenson/bats

[alandipert]

Totally, but we should hold off until namespaces, exceptions, and deftype are baked. Then we'll be able to have our own testing library :-)

[joelmccracken]

Yeah, though it's helpful to use tests even at this early stage

Sent from my iPhone

On Nov 19, 2013, at 11:31 AM, Alan Dipert [email protected] wrote:

Totally, but we should hold off until namespaces, exceptions, and deftype are baked. Then we'll be able to have our own testing library :-)

—
Reply to this email directly or view it on GitHub.

[quoll]

This has occurred to me as well.

Part of the reason I've been pushing things into core is to test out what
I'm doing. Stacking functions on top of each other ensures that the whole
framework is stable. It's not unit testing, but it does find problems.

However, the repl testing I'm doing can always be neglected, so it would be
nice to automate it a little. A simple file like test.gk could run a series
of assertions, with the expectation that they're all true. It's not much,
but it might be a start.

On Tue, Nov 19, 2013 at 6:01 PM, Joel McCracken [email protected]:

Yeah, though it's helpful to use tests even at this early stage

Sent from my iPhone

On Nov 19, 2013, at 11:31 AM, Alan Dipert [email protected]
wrote:

Totally, but we should hold off until namespaces, exceptions, and
deftype are baked. Then we'll be able to have our own testing library :-)

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-28847709
.