Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>MMMh since I'm using the TypeSafe stack I don't have access to the <code>play</code> executable.</p> <p>However, I know a way to start the play server in debug mode. Actually I wrote it on my blog <a href="http://ska-la.blogspot.be/2012/03/typesafe-stack-20-missing-play-debug.html" rel="nofollow">here</a>.</p> <pre><code>`export SBT_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9999` </code></pre> <p>will do the trick to have the JVM (running your Play server) listening for one debug connection.</p> <p>After what, you've said it, you setup a remote application that connect to <code>localhost:9999</code></p> <p>In the play console, you'll have the option to </p> <ul> <li>launch <code>test</code> and debug (in case you've unit test for your controller)</li> <li>test your app by hand (otherwise)</li> </ul> <p><strong>EDIT</strong></p> <p>Related to running the test in eclipse, I cannot see how to do since it relies on the classpath and probably some configuration.</p> <p>However what could be done is to execute <code>play debug test-only test.accounts.MyTest</code>, assuming you've a test called <code>MyTest</code> in the test classpath under the package <code>test.accounts</code>. This will execute only the MyTests's tests.</p> <p>While starting attach you debugger (remote app) to the jvm in order the walk the code.</p> <p>Another way might be : * <code>play debug</code> in one console, * attach the debugger * open an another console to execute <code>test-only test.accounts.MyTest</code> as many times as you want.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload