#1346 new
Yann Simon

play autotest does not execute tests

Reported by Yann Simon | January 2nd, 2012 @ 08:29 AM

Framework version: 1.2.4
Platform you're using: Linux (Ubuntu, OpenSuse)

Reproduction steps:
"play autotest" or "play auto-test" does not start.


The command output the following:
$ play auto-test
Listening for transport dt_socket at address: 8000
~ Go to http://localhost:9000/@tests to run the tests

and the tests are not executed.

By using git bisest, I found the commit that broke "autotest" (for #747):

The problem is in framework/pym/play/commands/base.py:

line 216:
- if line.find('/@tests to run the tests') > -1:
+ if line.find('Listening for HTTP') > -1:

On the tested system, the output is "Listening for transport" and not "Listening for HTTP".
Reverting this line-change fix "autotest".

Comments and changes to this ticket

  • Yann Simon

    Yann Simon January 2nd, 2012 @ 08:45 AM

    The problem is that "Listening for HTTP on port 9000 (Waiting a first request to start)" is written with the Logger.
    And the application is so configured that this line is written into a file, and not to the console output.

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