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
- Select one or more projects or folders and choose Search/File.
- Enter a string known to exist in multiple files and click
Replace
- Enter a new string that differs from the one searched for.
S2: Single file content modification
- Open a Java file that is read-only
- Perform any of the Java Source operations (e.g. toggle
comment)
- Ensure that validate edit is invoked
S3: Multiple file content modification
- Ensure all files in your workspace are read-only
- Perform a Java/Refactoring such as a method or class rename.
- Ensure that validate edit is invoked at most once per project
involved.