## Refactoring

Since:
Last Modified: $Date: 2004/06/14 20:44:55 $

These tests are a sanity check that workbench, JDT and other tools refactorings behave properly with respect to validate Edit. For a repository providers that supports a pessimistic workflow, the following scenarios should result in the invocation of the validate edit callback and should include a UI context which allows prompting.

The following scenarios are stated in terms of the Navigator view and JDT. Other tools should translate them to a set of scenarios that make sense for the tool.

### S1: Search and Replace

1. Select one or more projects or folders and choose Search/File.
2. Enter a string known to exist in multiple files and click Replace
3. Enter a new string that differs from the one searched for.

### S2: Single file content modification

1. Open a Java file that is read-only
2. Perform any of the Java Source operations (e.g. toggle comment)
3. Ensure that validate edit is invoked

### S3: Multiple file content modification

1. Ensure all files in your workspace are read-only
2. Perform a Java/Refactoring such as a method or class rename.
3. Ensure that validate edit is invoked at most once per project involved.