#1080 new
Sébastien Cesbron

autotest does not return an error if application to test does not start well

Reported by Sébastien Cesbron | August 29th, 2011 @ 02:34 PM

Framework version: 1.2.3
Platform you're using: linux

Reproduction steps:
1. Create an application
2. Define an evolution script and a database other than in memory
3. Start autotest without applying evolutions


When running the autotest command, if the application to test does not start the return code of the autotest command is 0.

For example, if you have database evolutions pending. You will have an output like that

~        _            _ 
~  _ __ | | __ _ _  _| |
~ | '_ \| |/ _' | || |_|
~ |  __/|_|\____|\__ (_)
~ |_|            |__/   
~ play! 1.2.3, http://www.playframework.org
~ framework ID is test
~ Running in test mode
~ Ctrl+C to stop
~ Deleting /home/sebastien/dev/projects/analytics/tmp
Listening for transport dt_socket at address: 8000
16:05:54,690 INFO  ~ Starting /home/sebastien/dev/projects/analytics
16:05:54,693 INFO  ~ Module secure is available (/usr/local/play-inst/play-1.2.3/modules/secure)
16:05:54,694 INFO  ~ Module cobertura is available (/home/sebastien/dev/projects/analytics/modules/cobertura-2.1)
16:05:55,292 WARN  ~ You're running Play! in DEV mode
~  Go to http://localhost:9000/@tests to run the tests
16:05:55,429 INFO  ~ Listening for HTTP on port 9000 (Waiting a first request to start) ...
~ The application does not start. There are errors: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:9000/@tests.list

and after that if you do

echo $?

the result is 0.

autotest command handle test failures but does not handle application start errors.

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