1
edit
Changes
no edit summary
<td>Wrapper around the necessary CVS commands</td>
<td>For the automated debugging to work, we may need to automatically modify the working copy by reverting to a different revision or updating certain directories and files. It may also need to know the differences between revisions and changesets.</td>
<td>[[User:RichardChudwwoodsi|Richard ChuDean Woodside]]</td> <td bgcolor="#FF0000">Not started. Will this be started before the end of the semester? i doubt it. After the end of the semester? most likelyJust starting out.</td>
</tr>
<td>Query CVS repository for differences between two revisions</td>
<td>Your mission is to find out the relevant commands that can return the differences between two revisions, the meta-data that is kept with each revision, how differences between two revisions are stored and formatted, and how this data can be parsed into a usable form for our project (wrapper?).</td>
<td>[[User:RichardChudwwoodsi|Richard ChuDean Woodside]]</td> <td bgcolor="#FF0000">Not started. Will this be started before the end of the semester? i doubt it. After the end of the semester? most likelyJust starting out.</td>
</tr>
<td>The Algorithm</td>
<td>The delta debugging algorithm. Drives the framework to retrieve change sets, apply changes, build source tree, run test case(s) to find the minimal set of failure inducing changes. The intersection of all other parts of the framework to make them work together. Ideally, should be abstract enough for easy extensibility with little impact.</td>
<td>[[User:dwwoodsiRichardChu|Dean WoodsideRichard Chu]]</td>
<td bgcolor="#FFFF00">Work in progress.</td>
</tr>
