| Line | |
|---|
| 1 | Test Suites |
|---|
| 2 | ===================== |
|---|
| 3 | |
|---|
| 4 | Currently the test suite need more formalized tests asap! I would |
|---|
| 5 | be ever greatful if people just keep pouring in tests that work but |
|---|
| 6 | illustrate and idea and even more greatful for tests which will cause |
|---|
| 7 | faults. Its a quick and easy way to get involved with language projects |
|---|
| 8 | since you get good experience in the language and in commiting to the |
|---|
| 9 | project and your name on the AUTHORS! |
|---|
| 10 | |
|---|
| 11 | How it works |
|---|
| 12 | ---------------- |
|---|
| 13 | |
|---|
| 14 | Currently, running make test in the toplevel invokes a perl script, to |
|---|
| 15 | read through the 't' directory for all the tests, and execute them and |
|---|
| 16 | compares the stdout stream with the contents of the respective filename |
|---|
| 17 | results file. Example if a test was called (test/t/t10.crl) the results |
|---|
| 18 | the desired result of this will be in (test/r/t10.r). So if these results |
|---|
| 19 | match it completes the test, this is what makes it important to have fairly |
|---|
| 20 | verbose messages in your tests so you have strings to match! |
|---|
