# HG changeset patch # User Doug Simon # Date 1351160996 -7200 # Node ID 1112609bb5dc9c6a2ae0035f3401689feca3c08f # Parent f170a0d2b3b9432008f30e8a4c3c6956e30d4a1d updated javadoc diff -r f170a0d2b3b9 -r 1112609bb5dc graal/com.oracle.graal.compiler.test/src/com/oracle/graal/compiler/test/GraalCompilerTest.java --- a/graal/com.oracle.graal.compiler.test/src/com/oracle/graal/compiler/test/GraalCompilerTest.java Thu Oct 25 12:29:39 2012 +0200 +++ b/graal/com.oracle.graal.compiler.test/src/com/oracle/graal/compiler/test/GraalCompilerTest.java Thu Oct 25 12:29:56 2012 +0200 @@ -44,8 +44,9 @@ import com.oracle.graal.phases.schedule.*; /** - * Base class for Graal compiler unit tests. These are white box tests - * for Graal compiler transformations. The general pattern for a test is: + * Base class for Graal compiler unit tests. + *

+ * White box tests for Graal compiler transformations use this pattern: *

    *
  1. Create a graph by {@linkplain #parse(String) parsing} a method.
  2. *
  3. Manually modify the graph (e.g. replace a parameter node with a constant).
  4. @@ -53,11 +54,13 @@ *
  5. Assert that the transformed graph is equal to an expected graph.
  6. *
*

- * See {@link InvokeHintsTest} as an example. + * See {@link InvokeHintsTest} as an example of a white box test. *

- * The tests can be run in Eclipse with the "Compiler Unit Test" Eclipse - * launch configuration found in the top level of this project or by - * running {@code mx unittest} on the command line. + * Black box tests use the {@link #test(String, Object...)} or {@link #testN(int, String, Object...)} + * to execute some method in the interpreter and compare its result against that produced + * by a Graal compiled version of the method. + *

+ * These tests will be run by the {@code mx unittest} command. */ public abstract class GraalCompilerTest {