myw/sehrvy — Issue #3: Pick a testing framework
Author: myw
Created: 2012-03-05 20:33:35+00:00
State: open

It seems like, for our simple purposes, `Test::Simple` and `Test::More` will do the trick. I propose making `t/Foo.t` files for every module we need, and maybe the scripts, too. They can then be run with the `prove` command from the directory with the module files. An individual `.t` file can `use` whichever testing module it needs to.

Although this structure is not explicitly enforced by the testing framework, we should try to make tests not too interdependent. And we should comment what every test is doing at the start of the testing block, for example:

```perl
# Check equality of exponentiation
my $foo = 3*3;
my $bar = 3**2;
ok($foo == $bar, 'exponentiation works');
```

Thoughts?