I have been using a bug reporting and tracking system called Mantis <http://en.wikipedia.org/wiki/Mantis_Bug_Tracker> which works quite well. For each bug, there is a test script which tests just that bug. I am suggesting these short test scripts in addition to the existing ones which are normally written as a feature is implemented. Being short and linked to the Mantis bug number, they are more easily identifiable *prima facie* case that a bug has been fixed.
Up to y'all, of course. Just a suggestion. On Mon, May 30, 2016 at 8:00 AM, Eric Iverson <eric.b.iver...@gmail.com> wrote: > I think Henry (and others) have been including updates to the existing test > scripts as appropriate when bugs are fixed or changes are made. > > Do you suggest that in addition to this (or perhaps instead of) that we > create a new test script for each fix? This might be better in the short > term, but I think integrating into existing scripts is better in the long > term. > > On Mon, May 30, 2016 at 8:41 AM, Roger Hui <rogerhui.can...@gmail.com> > wrote: > > > Suggestion: > > > > - As a bug is fixed a test script is written that tests the expression > > that exhibited the bug. > > - The previous is facilitated if the bugs were enumerated. > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
