Mohsen Vakilian

@Wanderer777: I created a class `p.C` that contained some compilation problems. Then, I renamed package `p` to `q`. After performing the refactoring, I consulted the `refactoring-problems.log` file, but, I didn't...

@Wanderer777 The script [find-outdated-fixed-change-sequences.rb](https://github.com/vazexqi/CodingSpectator/blob/master/scripts/svn-repository-analysis/find-outdated-fixed-change-sequences.rb) found only the following outdated fixed CodingTracker sequence: "relative path of fixed CodingTracker sequence","fixed revision","last changed revision" "cs-512/7e76e17c-a09e-4adf-8035-6841cad0d0e0/1.0.0.201107172332/codingtracker/codechanges.txt",2274,2335

@rajkuma1: Note that it's sufficient to convert the "refactoring-problems.log" into the CSV format. Once we generate the CSV file, we can easily import the CSV file into database tables (See...

@vazexqi, Would you add the query we wrote for listing the error messages of "change method signature" to `scripts/analysis-queries.sql`?

@Wanderer777: Does the SVN command line client exhibit the same behavior? That is, if one deletes a file from a working copy but not its `.svn` folder, will the file...

Test `pullup.T01` fails on Indigo because the `status` attribute is different in Indigo. And, `pullup.T02` fails on Indigo because the actual `refactoring-problems.log` file does not exist.

The UI tests exhibit similar behaviors on Indigo and Indigo SR1. The differences in Indigo SR1 with respect to Indigo are the following: - Test `pushdown.T03` fails on Indigo SR1...

I confirmed using CodingSpectator 1.0.0.201112231504 for Indigo SR1 that CodingSpectator does not record _redone_ refactorings.

@Wanderer777: I realized that it wasn't a good idea to match refactorings based on their timestamps and project names because the project names may change. Instead, I should compare refactorings...

@Wanderer777: The `edu.illinois.codingtracker.operations.refactorings.NewStartedRefactoringOperation.toString()` method doesn't print out the "description" attribute. For example, the "Operation Sequence View" shows the following information for an Extract Method refactoring: ``` Should always replay: false...