One of the options for running my tests in my game! the application will execute the command play auto-test.
One way to reproduce, apparently, identify the tests to run is to find all test classes with a superclass play.test.UnitTest(or other Play equivalent). Having an extension of the test class UnitTestseems to have some overhead, as shown in this snippet of material spit out in the console:
INFO info, Starting C:\projects\testapp\.
WARN warn, Declaring modules in application.conf is deprecated. Use dependencies.yml instead (module.secure)
INFO info, Module secure is available (C:\play-1.2.1\modules\secure)
INFO info, Module spring is available (C:\projects\testapp\.\modules\spring-1.0.1)
WARN warn, Actually play.tmp is set to null. Set it to play.tmp=none
WARN warn, You're running Play! in DEV mode
INFO info, Connected to jdbc:h2:mem:play;MODE=MYSQL;LOCK_MODE=0
INFO info, Application 'Test App' is now started !
Obviously, having a playback environment for tests that require this setup is useful, however, if I have a test class that checks production code that runs logic that does not require a playback environment, I don’t want to extend UnitTestso that I can avoid overhead when starting the playback environment.
If I have a test class that does not extend UnitTest, then it will not be executed by the command play auto-test. Is there a way to get the team play auto-testto run all the tests regardless of whether I extend the playback UnitTest?
Edit: Someone really raised a ticket for this same problem
source
share