anchor.diff:  
   .  First, you set breakpoints and/or watches before the problematic lines of code where you suspect the bug.
   **  If you want to watch a variable's value: Right-click on a variable and select New Watch from the context menu.
  -**  If you want to step through the execution line by line: Right-click on a line and choose Toggle Line Breakpoint; a pink box appears as a mark.
  +**  If you want to step through the execution line by line: btn:[RMB] click on a line and choose "`Toggle Line Breakpoint`"; a pink box appears as a mark.
   
   .  Choose menu:Debug[Debug Main Project] to start a debugger session for the whole project. Or, btn:[RMB] click a file and select "`Debug File`" to debug only one file.
   .  The application starts running normally. If you have set a breakpoint, the execution stops in this line. Debugger windows open and print debugger output.
   .  You can do many things now to track down a bug:
   **  Inspect the values of local variables.
   **  Use the Step buttons in the top to step into, out of, and over expressions while you watch the execution.
  -**  Navigate through your application's call stack. Right-click on threads to suspend or resume them.
  +**  Navigate through your application's call stack. btn:[RMB] click on threads to suspend or resume them.
   **  Choose menu:Debug[Evaluate Expression] from the menu to evaluate an expression.
   **  Move the mouse pointer over a variable to inspect its value in a tooltip.
   **  Inspect the classes loaded on the heap and the percentage and number of object instances. btn:[RMB] click a class in the Loaded Classes window and choose Show in Instances view (JDK 6 only).
  
positive.code: 
  If you do not see a Profiler menu in the jMonkeyEngine SDK, you need to download the Profiler plugin first.
  
  .  Open the Tools &gt; Plugins menu, and got to the “Available plugins tab
  .  Find the “Java Profiler plugin (“Java SE category) and check the Install box.
  .  Click the install button and follow the instructions.
  .  When you start the profiler for the first time, you are prompted to run a calibration once. Click OK in the “Profiler integration dialog to complete the installation process.
  
  
  === Monitoring and Analyzing
  
negative.code: 
  === Creating Tests
  
  .  btn:[RMB] click a Java file in the Projects window and choose menu:Tools[Create JUnit Tests].
  .  btn:[LMB]  click OK. The jMonkeyEngine SDK creates a JUnit test skeleton in the Test Package directory.
  .  The body of each generated test method is provided solely as a guide. In their place, you need to write your actual test cases!
  .  You can use tests such as `assertTrue(), assertFalse(), assertEquals()`, or `assert()`.
  **  The following example assertions test an addition method: `assert( add(1, 1) == 2); assertTrue( add(7,-5) == add(-5,7) )…`
  