do not run tests of play-tests itself
upgraded to Gradle 2.0
Release play-tests 3.1 with Selenide 2.12
smarter logging
Log tests execution time by class and by method
warmup play application before first test run
Calculate action coverage
print message with a single "print" command
find all controllers' methods
log actions coverage with play logger to avoid interleaving with other console output
duplicate logs of every test process to a separate file
first try to measure webdriver statistics.
measure times in nanoseconds.
log action coverage and webdriver statistics only in prod mode (on Jenkins)
log webdriver statistics only in prod mode (on Jenkins)
minor changes
fo not copy test classes to classpath for coverage
play-tests 3.4: log action coverage and webdriver statistics only in prod mode (on Jenkins)
ignore alert
code that is to be excluded from coverage calculations can be placed into the lib package
play-tests 3.5: avoid opening browser unless it's really needed