search

stainlessai / micronaut-jupyter

A Micronaut configuration that integrates your app with an existing Jupyter installation.
https://stainlessai.github.io/micronaut-jupyter
Apache License 2.0
9 stars 5 forks source link

MJ-25 ⁃ Separate unit and integration test tasks #23

Closed stainlessbot closed 4 years ago

stainlessbot commented 4 years ago

Currently, there is a separate gormTest task that always runs after the test task. This is because the dependencies for gorm conflict with the dependencies for micronaut data, and they can't both be used in the same app, or in this case gradle task.

There are several things about this that aren't ideal: If the --tests filter is used when running the test task, all of the tests in the gormTest task will still be run. The other kernel tests are slow integration style tests, and there is no way to just run the unit style tests

Create separate integrationTest and unitTest tasks. Both these tasks should be able to be filtered with --tests. Running the test task should run both of these tasks (and also apply the given --tests filter). Additionally, have the gorm functionality and micronaut data functionality be tested in separate gormTest and micronuatData test tasks, that are both run by integrationTest, so that their dependencies don't conflict (the remaining integration tests should be put into a third test task so that they can be run independent of the other two tasks).

┆Reporter: Joshua Carter ┆Issue Type: Story ┆Priority: High ┆Status: Resolved ┆Fix Versions: v0.2.1 ┆Issue Number: MJ-25 ┆Epic: Testing & DevOps

stainlessbot commented 4 years ago

➤ Joshua Carter commented:

Currently, the --tests filter actually does work on the gormTest task individually.

stainlessbot commented 4 years ago

➤ Joshua Carter commented:

The micronaut data test task will be named mdTest.

JoshuaCWebDeveloper commented 4 years ago

I couldn't get the --tests option to apply to subtasks, so a separate -Ptest option will have to be used.

Now that the tasks are separated, the test reports are in separate directories, FYI.