blob: 5b16166e6ce24d7549ce3076545636f0f837830b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
<html>
<head>
<title>Refactoring</title>
<LINK REL=STYLESHEET HREF=../book.css CHARSET=ISO-8859-1 TYPE=text/css>
<meta NAME="keywords" content="">
<meta NAME="since" content="">
</head>
<h2>Refactoring</h2>
<p>Since: <br>
Last Modified: $Date: 2004/06/14 20:44:55 $</p>
<body>
<p>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.
<p>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.</p>
<!-- ------------------------------------------------------------------------------ -->
<h3>S1: Search and Replace</h3>
<ol>
<li>Select one or more projects or folders and choose Search/File.</li>
<li>Enter a string known to exist in multiple files and click
Replace</li>
<li>Enter a new string that differs from the one searched for.</li>
</ol>
<!-- ------------------------------------------------------------------------------ -->
<h3>S2: Single file content modification</h3>
<ol>
<li>Open a Java file that is read-only</li>
<li>Perform any of the Java Source operations (e.g. toggle
comment)</li>
<li>Ensure that validate edit is invoked</li>
</ol>
<!-- ------------------------------------------------------------------------------ -->
<h3>S3: Multiple file content modification</h3>
<ol>
<li>Ensure all files in your workspace are read-only</li>
<li>Perform a Java/Refactoring such as a method or class rename.</li>
<li>Ensure that validate edit is invoked at most once per project
involved.</li>
</ol>
</body>
</html>
|
