1
edit
Changes
→Project News
''This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.''
=== Dec. 22, 2006 ===
I haven't posted an update in a while. So what's been done?
I finally had some time to do a second round of testing & debugging of the delta debugging framework. And guess what? It ''seems'' to work now. The problem? Combination of logical errors when applying and unapplying changes in the framework and a bad test case. Go figure.
However, before I get ahead of myself and officially tag and release the delta debugging framework as version 0.1, I would like to test it out on another test program. Hopefully, this can be done this weekend. And if all goes well, version 0.1 will be officially released before the end of the year.
=== Dec. 13, 2006 ===
A roadmap of our vision of the direction of the project will be heading in the future will be created and posted soon.
=== Dec. 11, 2006 ===
Uploaded testcase for '''HelloWorld''' binary at '''deltatest svn'''. The test simulates the error that may occur when compilation fails due to syntax error. The exalted HelloWorld program is located on the HelloWorld directory, while the test definition is at HelloTestCase1.pm. The algorithm detects failed test and reverts the affected file to the version where the test passes.
Note for the future: improve user feedback functions!
=== Dec. 10, 2006 ===
Where is the CVS/Bonsai work heading? Here is a breakdown of the past 3-4 weeks:
* Initially was going for a straight wrapper around CVS ala the style Richard used for SVN.
=== Dec. 09, 2006 ===
What has been done since last week?
* Got a test program and uploaded it to svn://cdot.senecac.on.ca/deltatest. The pristine working version is revision 4. The latest committed copy is revision 8. The regressive code was committed somewhere in between.
=== Dec. 03, 2006 ===
Committed some updated to the SVN repository.
* The test framework. There are a couple of files to the framework: Test.pl, TestCase.pl, TestSuite.pl, TestResult.pl, TestRunner.pl. It is loosely based off of the design of the JUnit framework. Why such an elaborate design just for the need of users to define the test case that can determine whether or not a piece of functionality works or not to be run? For a few reasons that I may be adamant about:
=== Nov. 26, 2006 ===
Committed some updates to the SVN repository.
* Updated the delta debugging algorithm module. I didn't realize this yesterday but the algorithm to find the minimal set of failure inducing files (and code block and line of code changes if those changeset types ever gets dones) is the same (with minor modifications) as the algorithm that can find the minimal set of failure inducing directories. Thus I generalized that algorithm to remove the directory changeset specific code so that it will work with all other types of changesets.
=== Nov. 25, 2006 ===
I haven't posted an update in a while so here goes. What's been done since then?
=== Nov. 19, 2006 ===
The earlier crash case we had (see the update directly below) was a non-regressive bug--there was no former build that worked with it.
=== Nov. 18, 2006 ===
*<strike>Found a suitable crash case thanks to the people of [irc://irc.mozilla.org#qa #qa] (in particular, asqueella and Aleksej). For full details on the bug, see [https://bugzilla.mozilla.org/show_bug.cgi?id=354300 Bug #354300].</strike>