Closed gortiz closed 7 years ago
I have discarted the approach that uses a category to classify test between unit and integration tests, as it has some problems related to the class not being found by surefire on the same project that is compiling it. Therefore, we have to use class names to classify tests. All classes whose name is Test are unit tests and tests whose name is IT are integration tests.
Merging #163 into devel will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## devel #163 +/- ##
=========================================
Coverage 18.33% 18.33%
Complexity 1513 1513
=========================================
Files 780 780
Lines 26823 26823
Branches 2340 2340
=========================================
Hits 4917 4917
Misses 21572 21572
Partials 334 334
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 54da944...a4ecb36. Read the comment docs.
Our first iteration on the integration framework used a specific folder under each project to classify tests as unit test or integration tests. It works fine, but IDEs require some configuration to recognized the folder. We have change that to use a more standard approach on which tests are, by default, unit tests, but can be annotated with @Category(IntegrationTest.class*) to indicate they are integration tests and therefore must be ignored by surefire pluging and executed with failsafe plugin
* IntegrationTest.class is on the core module