You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2019/07/12 09:41:00 UTC
[jira] [Updated] (CAMEL-13629) Some tests are excluded from maven
build because of wrong class name
[ https://issues.apache.org/jira/browse/CAMEL-13629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Cosentino updated CAMEL-13629:
-------------------------------------
Fix Version/s: 3.0.0.M5
3.0.0
> Some tests are excluded from maven build because of wrong class name
> --------------------------------------------------------------------
>
> Key: CAMEL-13629
> URL: https://issues.apache.org/jira/browse/CAMEL-13629
> Project: Camel
> Issue Type: Test
> Reporter: Jan Bednar
> Assignee: Jan Bednar
> Priority: Minor
> Fix For: 3.0.0, 3.0.0.M5
>
> Attachments: grepResult.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are some tests, which were probably meant to run during build, but does not follow .*Test.java or *IT.java filename pattern.
>
> This returns 46 files on current master (output attached):
> {code:java}
> grep -rnw './camel' --include=\*.java -e '@Test' -l | grep -v -e '.*Test.java' -e '.*TestSupport.java' -e '.*TestBase.java' -e '.*IT.java'
> {code}
> This method is not bulletproof and returns some false-positives, but most of the matches should be IMO renamed to follow filename patternt and thus be executed during maven build.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)