search

vazexqi / CodingSpectator

Watches and analyzes code edits in the Eclipse IDE non-invasively
http://codingspectator.cs.illinois.edu
Other
20 stars 14 forks source link

CodingTracker tasks that should be completed before the release #186

Closed Wanderer777 closed 13 years ago

Wanderer777 commented 13 years ago

It would be good to complete the following tasks before CodingTracker is available to our study participants:

  1. Fix the problem when refreshing an out-of-sync file is recorded as a performed edit and confuses the state of the recorder (e.g. sometimes this external modification is recorded as a file save, the document is considered dirty while it is not, etc.).
  2. Investigate and fix issue #177 (the replay error part, if it is related to problems during the recording).
  3. Fix issue #203 and add tests that would check record/replay of all automated Eclipse refactorings.
  4. Replay all data collected from students in the previous study. Investigate and fix any additional problems in the recorder.
Wanderer777 commented 13 years ago

Item (1) is fixed in a4ac1d35352e885b5d72790afa4e747c77ccbdcc

Wanderer777 commented 13 years ago

Item (2) is fixed by 7052e0729d56fda3c35bd338c328331c5222b64c and 4a9733488c9bad2335e1167ca514e1bcb8a7482c

Wanderer777 commented 13 years ago

Item (3) is partially addressed in 3a2abb9a8ca91ad87667b76181dbeeccdf1343b4

Wanderer777 commented 13 years ago

Item (3) is fixed in issue #203. Item (4) is partially addressed by replaying some of the long sequences and fixing the found problems. Problems in replaying of other sequences are (or would be) reported as individual issues and will be addressed after the release.