The plan calls for continuous integration. That is, automating the process of doing releases so that every new change becomes a new release.
Part of that process involves running a test suite to make sure that nothing broke, a process currently done by hand. If something does break, a new test is added. We are trying to build a more expansive suite of tests. You can help. In particular, you can make sure that things you care about and depend upon become part of the test suite. Ideally a test set would include an explanation, since not everyone does Mellin transforms, or whatever your specialty is. But that isn't required. Any input file you use for testing is fine. At this point it is more important to gather the test sets. Please create an input file, run it, capture the output, and send it. That is, create mytestset.input )spool mytestset.output 3+5 6+7 )spool run it, CHECK THAT THE ANSWERS ARE CORRECT, and send "mytestset.output" to [email protected] Even simple, seemingly mundane test suites can uncover failures. Please help. Tim _______________________________________________ Axiom-developer mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/axiom-developer
