#665 new
Martin Polden

Exception when loading testrunner module explicitly

Reported by Martin Polden | March 20th, 2011 @ 12:34 PM

As far as I understand 'play test' addes the testrunner module to the classpath automatically.

When I create a run configuration in IntelliJ IDEA for running Play in test-mode, I need to explicitly load the testrunner either by setting the MODULES environment variable or by setting %test.module.testrunner=${play.path}/modules/testrunner in application.conf. Adding just -Dplay.id=test to the VM parameters does not work and does not load the testrunner module.

When loading the testrunner module explicitly, returns the following error:

Compilation error

The file {module:testrunner}/app/controllers/TestRunner.java could not be compiled. Error raised is : The type TestRunner is already defined In {module:testrunner}/app/controllers/TestRunner.java (around line 18)

14: import play.templates.TemplateLoader;
15: import play.test.*;
16: import play.vfs.*;
18: public class TestRunner extends Controller {
20:     public static void index() {
21:     List<Class> unitTests = TestEngine.allUnitTests();
22:     List<Class> functionalTests = TestEngine.allFunctionalTests();
23:     List<String> seleniumTests = TestEngine.allSeleniumTests();
24:     render(unitTests, functionalTests, seleniumTests);

I could set the test ID to something different, like ideatest but then the test routes won't be loaded.

Play Framework version: 1.1.1
Platforms: Ubuntu 10.10 amd64 and Windows 7 x64 SP1

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.