-
Notifications
You must be signed in to change notification settings - Fork 682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Play should run its own tests in precompiled mode #1154
Comments
and why not just run
? The above approach is used by us on jenkins runs but we also use our own liquibase module
The lb:install will just apply fresh install migrations, the lb:update will do more or less nothing on a fresh install, but creation of views (for reports) is also handled by lb:update. |
@flybyray Yes, you can run tests of some application this way. |
do you mean |
Oh, sorry. Yes! I meant |
just updated the first comment. but maybe you see reason for DEV-mode and empty db. that applies to most of the tests to. you should add jpa ddl update for prod in this case too |
some tests have bootstrap jobs which load data, in case the data yaml cotains templates you will need to precompile them too (this was just fixed some tickets ago). but you need to specify those templates in application.conf |
ok just checked none of the tests seem to have initial data with templates. from my point of view this is a missing code coverage |
|
Hi, We're trying to get coverage working on our play tests with JaCoCo. Are you aware of any way to get this working with Play framework? We're running 1.4.2 at the moment. I'm also interested to know if we can use ant directly to run tests too. |
@Fraserhardy As much as I know, it's not possible. The problem is that JaCoCo needs to modify bytecode of your application, but Play also modifies the bytecode of your application. Those two frameworks conflict with each other. |
@asolntsev Are you aware of any coverage tools that work with Play 1? |
The problem I mentioned is actual for any other coverage tool. So I think
it's basically not possible with Play 1.
…On Feb 22, 2018 15:36, "Fraserhardy" ***@***.***> wrote:
@asolntsev <https://github.com/asolntsev> Are you aware of any coverage
tools that work with Play 1?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1154 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARE3b7kLI-YzJDU6SyU1tv3SKhZvxpSks5tXW1agaJpZM4Nn7OS>
.
|
Should the codecoverage only be used interactively or should it be evaluated automatically? |
@flybyray Even within IntelliJ would be a massive bonus at the moment. We have had mixed success with test running direct in IntelliJ so far but I'll certainly try those steps from the video. Sounds like we need a PR to fix the Intellij template for Play then? |
the templating for various ides is outdated. take the eclipse templates for example. create a project with a module. add tests to your module. |
Currently play own tests are executed in
DEV
mode.Thus they will not catch any errors that happen only in
PROD
mode (for example, see issue #1152).I believe we should run play tests in
PROD
mode. It will give stronger confidence that application works in production as in test.The text was updated successfully, but these errors were encountered: