#1628 ✓resolved
Jesper Rønn-Jensen

Play testrunner. Rerun failed tests first

Reported by Jesper Rønn-Jensen | December 30th, 2012 @ 03:56 PM | in 1.3 (closed)

I created a change for the HTML/Javascript testrunner. Now it fails faster, since tests that have previously failed are run first.

The change is really simple. In the test runner js, i run through all tests that fail and annotate them. Once the testrunner determines which test to run next, it will prioritize the ones that previously failed. After that, it continues to pick next test like before.

Currently we use it at work with Play 1.2.4.

I am interested in any feedback you have:

  • Does it work for you?
  • Improvement suggestions and patches
  • How to push this into the official Play stream?

Framework version: 1.2.4
Platform you're using: unix

See Google group discussion: https://groups.google.com/forum/#!msg/play-framework/8D1aRLPE1Uo/xX...
and https://github.com/playframework/play/pull/523#issuecomment-11758744

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.