Changes

Jump to: navigation, search

Delta debugging framework

1,340 bytes added, 02:23, 4 December 2006
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. 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:
# To use the delta debugging framework, the user should not have to touch the DeltaDebugger.pl file to define the tests and how to run them. Using the testing framework, this can be done by subclassing the TestCase.pl class and overriding the run() subroutine.
# For the delta debugger to work, it needs to know whether the test case passes or fails. Using the test framework, I hope to control the possible return codes of the tests to either pass or fail only.
* testtest.pl that tests the functionality of the test framework.
* updates to DeltaDebugger.pl to make use of the test framework.
 
 
Crunch time. One week left. The high priority tasks that still need to be done:
# Acquisition of a program we could use to test the delta debugging framework. See [[#How_to_Get_Involved|How To Get Involved]] for more info.
# Test, debug the delta debugging framework.
'''Milestone:'''
* Even though the test framework is incomplete, I think we can go ahead and begin the initial testing of the delta debugger on a real regressive program as I think we are ready. Coincidentally, exactly 2 months after the first project news posting on Sept. 26, 2006.
 
=== Nov. 25, 2006 ===
1
edit

Navigation menu