[
https://issues.apache.org/jira/browse/IGNITE-18251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-18251:
-----------------------------------
Description:
Currently, TeamCity runs tests twice, because test classes are not specified.
It leads to running of both suite classes and test classes, included to this
test suites. Arguments are listed below [1]:
{code}
-pl modules/%DIR_EXTENSION% -am
-Dmaven.test.failure.ignore=true
-DfailIfNoTests=false
-Dignite.version=%IGNITE_VERSION%
{code}
Also, there are following problems:
# Timeouts of CDC Suite
# Zookeeper Ip Finder and AOP has no running test on TC [2, 3].
What should be done:
# Split {{IgniteCdcTestSuite}} class on two separate classes.
# Make two separate TC builds for corresponding CDC suite classes. To control
abandoned tests profile {{check-test-suites}} from Ignite must be used (see
IGNITE-18252).
# {{failIfNoTests}} should be set to 'true' in order to prevent situations when
module was not tested (see IGNITE-18252).
# Fix Zookeeper Ip Finder and AOP modules testing.
Links:
#
https://ci2.ignite.apache.org/admin/editRunType.html?id=template:IgniteExtensions_Tests_RunExtensionTests&runnerId=RUNNER_141&cameFromUrl=%2Fadmin%2FeditBuildRunners.html%3Fid%3Dtemplate%253AIgniteExtensions_Tests_RunExtensionTests%26init%3D1&cameFromTitle=
#
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_ZookeeperIpFinder?branch=&mode=builds#all-projects
#
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?mode=builds#all-projects
P.S.
*_So, there are possible solutions:_*
# Remove {{IgniteCdcTestSuite}} class without changing TC confiuration.
# Split {{IgniteCdcTestSuite}} onto to suite classes, eg. Ignite2Ignite and
IgniteThroughKafka. This also makes possible to run suites separately, but
requires changing TC configuration.
Also, we can add explicit suite classes in TC configuration, but it is makes
sense only if we have to to run suites in parallel manner for some modules. If
I'm right, only CDC is now a possible candidate for this.
was:
Currently, TeamCity runs tests twice, because test classes are not specified.
It leads to running of both suite classes and test classes, included to this
test suites. Arguments are listed below [1]:
{code}
-pl modules/%DIR_EXTENSION% -am
-Dmaven.test.failure.ignore=true
-DfailIfNoTests=false
-Dignite.version=%IGNITE_VERSION%
{code}
Also, there are following problems:
# Timeouts of CDC Suite
# Zookeeper Ip Finder and AOP has no running test on TC [2, 3].
What should be done:
# Split {{IgniteCdcTestSuite}} class on two separate classes.
# Make two separate TC builds for corresponding CDC suite classes. To control
abandoned tests profile {{check-test-suites}} from Ignite must be used (see
IGNITE-18252).
# {{failIfNoTests}} should be set to 'true' in order to prevent situations when
module was not tested (see IGNITE-18252).
# Fix Zookeeper Ip Finder and AOP modules testing.
Links:
#
https://ci2.ignite.apache.org/admin/editRunType.html?id=template:IgniteExtensions_Tests_RunExtensionTests&runnerId=RUNNER_141&cameFromUrl=%2Fadmin%2FeditBuildRunners.html%3Fid%3Dtemplate%253AIgniteExtensions_Tests_RunExtensionTests%26init%3D1&cameFromTitle=
#
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_ZookeeperIpFinder?branch=&mode=builds#all-projects
#
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?mode=builds#all-projects
P.S.
*_So, there are possible solutions:_*
# Remove {{IgniteCdcTestSuite}} class without changing TC confiuration.
# Split {{IgniteCdcTestSuite}} onto to suite classes, eg. Ignite2Ignite and
IgniteThroughKafka. This also makes possible to run suites separately, but
requires changing TC configuration.
Also, we can add explicit suite classes in TC configuration, but it is makes
sense only if we have to to run suites in parallel manner for some modules. If
I'm right, only CDC is now a possible candidate for this.
> Refactor testing of ignite-extensions
> -------------------------------------
>
> Key: IGNITE-18251
> URL: https://issues.apache.org/jira/browse/IGNITE-18251
> Project: Ignite
> Issue Type: Task
> Components: extensions
> Reporter: Ilya Shishkov
> Priority: Major
> Labels: ise, teamcity
>
> Currently, TeamCity runs tests twice, because test classes are not specified.
> It leads to running of both suite classes and test classes, included to this
> test suites. Arguments are listed below [1]:
> {code}
> -pl modules/%DIR_EXTENSION% -am
> -Dmaven.test.failure.ignore=true
> -DfailIfNoTests=false
> -Dignite.version=%IGNITE_VERSION%
> {code}
> Also, there are following problems:
> # Timeouts of CDC Suite
> # Zookeeper Ip Finder and AOP has no running test on TC [2, 3].
> What should be done:
> # Split {{IgniteCdcTestSuite}} class on two separate classes.
> # Make two separate TC builds for corresponding CDC suite classes. To control
> abandoned tests profile {{check-test-suites}} from Ignite must be used (see
> IGNITE-18252).
> # {{failIfNoTests}} should be set to 'true' in order to prevent situations
> when module was not tested (see IGNITE-18252).
> # Fix Zookeeper Ip Finder and AOP modules testing.
> Links:
> #
> https://ci2.ignite.apache.org/admin/editRunType.html?id=template:IgniteExtensions_Tests_RunExtensionTests&runnerId=RUNNER_141&cameFromUrl=%2Fadmin%2FeditBuildRunners.html%3Fid%3Dtemplate%253AIgniteExtensions_Tests_RunExtensionTests%26init%3D1&cameFromTitle=
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_ZookeeperIpFinder?branch=&mode=builds#all-projects
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?mode=builds#all-projects
> P.S.
> *_So, there are possible solutions:_*
> # Remove {{IgniteCdcTestSuite}} class without changing TC confiuration.
> # Split {{IgniteCdcTestSuite}} onto to suite classes, eg. Ignite2Ignite and
> IgniteThroughKafka. This also makes possible to run suites separately, but
> requires changing TC configuration.
> Also, we can add explicit suite classes in TC configuration, but it is makes
> sense only if we have to to run suites in parallel manner for some modules.
> If I'm right, only CDC is now a possible candidate for this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
