#1257 ✓invalid
John Gnip

Test mode is like normal mode

Reported by John Gnip | November 16th, 2011 @ 08:11 AM | in 1.3 (closed)

I'm having a little problem with command "play test" or "play auto-test"...The first command gives me something like this:

My-heaven:jobboard Droid$ play test
~        _            _ 
~  _ __ | | __ _ _  _| |
~ | '_ \| |/ _' | || |_|
~ |  __/|_|\____|\__ (_)
~ |_|            |__/   
~
~ play! 1.2.3, http://www.playframework.org
~ framework ID is test
~
~ Running in test mode
~ Ctrl+C to stop
~ 
Listening for transport dt_socket at address: 8000
23:07:33,827 INFO  ~ Starting /Users/Droid/Downloads/play-1.2.3/play-1.2.3/samples-and-tests/jobboard
23:07:33,832 WARN  ~ Declaring modules in application.conf is deprecated. Use dependencies.yml instead (module.crud)
23:07:33,833 INFO  ~ Module crud is available (/Users/Droid/Downloads/play-1.2.3/play-1.2.3/modules/crud)
23:07:34,858 WARN  ~ You're running Play! in DEV mode
23:07:35,020 INFO  ~ Listening for HTTP on port 9000 (Waiting a first request to start) ...

And http://localhost:9000/@tests shows me, that the route wan't found. After "play auto-test", the output looks like this:

My-heaven:jobboard Droid$ play auto-test
~        _            _ 
~  _ __ | | __ _ _  _| |
~ | '_ \| |/ _' | || |_|
~ |  __/|_|\____|\__ (_)
~ |_|            |__/   
~
~ play! 1.2.3, http://www.playframework.org
~ framework ID is test
~
~ Running in test mode
~ Ctrl+C to stop
~ 
~ Deleting /Users/Droid/Downloads/play-1.2.3/play-1.2.3/samples-and-tests/jobboard/tmp
~
Listening for transport dt_socket at address: 8000
23:09:29,670 INFO  ~ Starting /Users/Droid/Downloads/play-1.2.3/play-1.2.3/samples-and-tests/jobboard
23:09:29,678 WARN  ~ Declaring modules in application.conf is deprecated. Use dependencies.yml instead (module.crud)
23:09:29,679 INFO  ~ Module crud is available (/Users/Droid/Downloads/play-1.2.3/play-1.2.3/modules/crud)
23:09:30,913 WARN  ~ You're running Play! in DEV mode
23:09:31,077 INFO  ~ Listening for HTTP on port 9000 (Waiting a first request to start) ...
~
Exception in thread "main" java.lang.NoClassDefFoundError: play/modules/testrunner/FirePhoque
Caused by: java.lang.ClassNotFoundException: play.modules.testrunner.FirePhoque
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
~

Is that OK?

Framework version:
1.2.3

OS:
MacOS 10.6.8

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket

Referenced by

Pages