FeaturesPluginsDocs & SupportCommunityPartners

Jellytools Test Cases Debugging - NetBeans 3.6

Author: Jiri Skrivanek
Last update: April 22, 2002


This page should help you to debug your tests inside IDE.

Step by step guide

You need two instances of IDE running at the same time. Actions in first IDE will be marked by green color, actions in second IDE by blue color.
 
  • start a first IDE which will be used as a debugger
  • mount jemmy (jar or sources)
  • mount jellytools (jar or sources)
  • mount directory with your test case
  • start a second IDE in debugging mode using following command line parameters
    runide.sh -userdir debugUserdir -J-Xdebug -J-Xnoagent -J-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8765
Note: You can use the same userdir as for the first IDE. It will save you mounting all resources but it can clutter your userdir.
  • mount jemmy (jar or sources)
  • mount jelly (jar or sources)
  • mount directory with your test case
  • connect from first IDE to the second
    • from main menu choose: Debug -> Attach
    • fill in Attach to VM dialog
      • Debugger Type: (JPDA)
      • Transport: dt_socket
      • Host: <your_host_name>
      • Port: 8765
    • wait for Debugger Window opened and message "Connection established" appeared in the Output Window
  • add breakpoint(s) to the test case source code
  • run the test in the second (debugged) IDE (be sure to set Internal Executor for it)
  • the test should stop at the breakpoint and you should be able normally debug code in first IDE and see actions in the second IDE


If you find a problem, please look at detailed guide how to debug NetBeans IDE with the NetBeans debugger.
 
 
 
 

Companion
Projects:
MySQL Database Server   Open JDK: an Open SourceJDK   GlassFish Community: an Open Source Application Server    Mobile & Embedded Community    Open Solaris   java.net - The Source for Java Technology Collaboration   Virtual Box - full virtualizer  Open ESB - The Open Enterprise Service Bus Powered by