Added a testsuite. This currently only has one test, which replicates a problem...
authorRichard Boulton <richard@tartarus.org>
Fri, 9 Mar 2001 12:08:38 +0000 (12:08 +0000)
committerRichard Boulton <richard@tartarus.org>
Fri, 9 Mar 2001 12:08:38 +0000 (12:08 +0000)
commit51847f3fe43698d3bc20f8324cf10ef89000cb71
tree2c8e256b4d6588081472bd793a64d6385d8001ab
parentce2a73264057cf38f79a1e1d7c131c48fc682e7c
Added a testsuite.  This currently only has one test, which replicates a problem just submitted to the list.

Original commit message from CVS:
Added a testsuite.  This currently only has one test, which replicates a
problem just submitted to the list.

I hope noone disagrees that we need a testsuite.  Also, hopefully we all
think that a tiny testsuite which is easy to add tests to is much better
than a huge project to create a complete testsuite, which never gets
started because its too big and scary.

I suggest that tests get created whenever someone has a spare moment, or
whenever a bug is reported (to replicate the problem, and thus be sure that
when fixed it stays fixed), and before making a change to a piece of code
to ensure that it remains working.

If we all add little tests occasionally, then we'll have a good useful
testsuite before we know it.  All you need to do is make a
Makefile.am
configure.in
tests/old/testsuite/Makefile.am [new file with mode: 0644]
tests/old/testsuite/test_gst_init.c [new file with mode: 0644]
testsuite/Makefile.am [new file with mode: 0644]
testsuite/test_gst_init.c [new file with mode: 0644]