Feature request: Run JUnit tests not extending BaseTest
The Play TestEngine only loads classes that are assignable from org.junit.Assert (i.e. which extend BaseTest, UnitTest or FunctionalTest). However, these incur an overhead in the time it takes to spin up the Play environment when running the tests in Eclipse, especially with a not-so-trivial set of models and a few modules. For many classes that are not models or controllers, this is an unnecessary and annoying overhead that significantly slows development if you choose to run tests in Eclipse (preferable) rather than in the browser. In my current project, it takes 10-20 seconds to run a single test class, as opposed to under 1 second if I don't extend UnitTest.
Ideally Play should discover and run all tests, regardless of whether or not they extend BaseTest.
Current workaround is to extend org.junit.Assert directly - this is not too bad but I'd like to just write classes normally where at all possible.
Comments and changes to this ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
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 http://www.playframework.org website.
Source code is hosted on githubCheck out our repository at http://github.com/playframework/play
Contributing, creating a patchPlease read the contributor guide
Reporting Security VulnerabilitiesSince all bug reports are public, please report any security vulnerability directly to guillaume dot bort at gmail dot com.
Creating a bug reportBug 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.
Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.
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.