[
https://issues.apache.org/jira/browse/DERBY-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660791#action_12660791
]
Dag H. Wanvik commented on DERBY-3998:
--------------------------------------
"Kristian Waagan (JIRA)" <[email protected]> writes:
> FYI, the script found tests by looking for files named '*Test.java' in the
> java/testing/org/apache/derbyTesting/functionTests directory. I have not
> checked if there are JUnit tests that don't follow the naming scheme. All the
> processing was done by searching the source code.
Here are some JUnit importing files, minus some obvious known special
cases. Some of the remaining are setup classes according to their
naming (it would be good if all such would use the suffix 'Setup'),
some deviate from naming scheme, e.g. FullCollationTests.
> cd java/testing/org/apache/derbyTesting/
> find . -name '*.java' |xargs egrep -l 'import.*junit.*' /dev/null | grep -v
> 'Test.java' | grep -v '_Suite.java' | grep -v 'functionTests/suites' | grep
> -v replicationTests | grep -v upgradeTests | grep -v '[.]/junit'
./functionTests/harness/jvm.java
./functionTests/tests/derbynet/DerbyNetNewServer.java
./functionTests/tests/derbynet/testProtocol.java
./functionTests/tests/derbynet/CheckSecurityManager.java
./functionTests/tests/jdbc4/BlobClobTestSetup.java
./functionTests/tests/jdbc4/CallableStatementTestSetup.java
./functionTests/tests/jdbc4/StatementTestSetup.java
./functionTests/tests/jdbc4/TestDbMetaData.java
./functionTests/tests/jdbc4/TestJDBC40Exception.java
./functionTests/tests/jdbc4/UnsupportedVetter.java
./functionTests/tests/jdbc4/VerifySignatures.java
./functionTests/tests/jdbcapi/BLOBDataModelSetup.java
./functionTests/tests/jdbcapi/SURDataModelSetup.java
./functionTests/tests/junitTests/compatibility/CompatibilitySuite.java
./functionTests/tests/junitTests/compatibility/CompatibilityCombinations.java
./functionTests/tests/junitTests/compatibility/BLOBCLOB_CompatibilitySuite.java
./functionTests/tests/lang/LangScripts.java
./functionTests/tests/lang/PrepareExecuteDDL.java
./functionTests/tests/lang/CollationTest2.java
./functionTests/tests/lang/TableVTI.java
./functionTests/tests/lang/FullCollationTests.java
./functionTests/tests/lang/largeCodeGen.java
./functionTests/tests/lang/GeneratedColumnsHelper.java
./functionTests/tests/memory/ConnectionHandlingJunit.java
./functionTests/tests/nist/NistScripts.java
./functionTests/tests/tools/ToolScripts.java
./functionTests/tests/management/JMXConnectionDecorator.java
./functionTests/tests/multi/StressMulti10x1.java
./functionTests/tests/multi/StressMulti50x59.java
./functionTests/util/CanonTestCase.java
./functionTests/util/ScriptTestCase.java
./functionTests/util/SecurityCheck.java
./functionTests/util/IjTestCase.java
./system/oe/test/OperationsTester.java
./system/oe/run/Checks.java
./system/oe/run/Schema.java
./system/oe/run/Populate.java
./perf/basic/jdbc/CoveredIdxScan.java
./perf/basic/jdbc/BaseLoad100IdxTestSetup.java
./perf/basic/jdbc/HeapScan.java
./perf/basic/jdbc/BaseLoad100TestSetup.java
To see which of these are actually run from a _Suite.java file, I did:
find . -name '_Suite.java' |xargs grep '.suite()' | grep -v 'Test.suite()'
./functionTests/tests/derbynet/_Suite.java:
//suite.addTest(CheckSecurityManager.suite());
./functionTests/tests/jdbc4/_Suite.java:
suite.addTest(TestDbMetaData.suite());
./functionTests/tests/jdbc4/_Suite.java:
suite.addTest(TestJDBC40Exception.suite());
./functionTests/tests/jdbc4/_Suite.java:
suite.addTest(UnsupportedVetter.suite());
./functionTests/tests/jdbc4/_Suite.java:
suite.addTest(VerifySignatures.suite());
./functionTests/tests/lang/_Suite.java: //
suite.addTest(largeCodeGen.suite());
./functionTests/tests/lang/_Suite.java:
suite.addTest(LangScripts.suite());
./functionTests/tests/lang/_Suite.java:
suite.addTest(PrepareExecuteDDL.suite());
./functionTests/tests/lang/_Suite.java:
suite.addTest(CollationTest2.suite());
./functionTests/tests/lang/_Suite.java: suite.addTest(XMLSuite.suite());
./functionTests/tests/lang/_Suite.java:
suite.addTest(NistScripts.suite());
./functionTests/tests/tools/_Suite.java:
suite.addTest(ToolScripts.suite());
./perf/basic/_Suite.java: suite.addTest(HeapScan.suite());
./perf/basic/_Suite.java: suite.addTest(CoveredIdxScan.suite());
> Make sure all JUnit tests are run as part of a suite
> ----------------------------------------------------
>
> Key: DERBY-3998
> URL: https://issues.apache.org/jira/browse/DERBY-3998
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
>
> I discovered that all tests are not being run as part of a suite. This should
> be fixed.
> Based on the output from a little Python script I wrote and some
> investigation, I ended up with the following list of tests that *might*
> require some maintenance:
> # Non-JUnit tests - breaks the naming scheme
> java/testing/org/apache/derbyTesting/functionTests/tests/store/EncryptionTest.java
> java/testing/org/apache/derbyTesting/functionTests/tests/lang/GetPropertyInfoTest.java
> java/testing/org/apache/derbyTesting/functionTests/tests/store/LogDeviceTest.java
> java/testing/org/apache/derbyTesting/functionTests/tests/store/OnlineCompressTest.java
> # Disabled to to bugs or product defects
> java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/Derby3650Test.java
> java/testing/org/apache/derbyTesting/functionTests/tests/store/Derby3980DeadlockTest.java
> java/testing/org/apache/derbyTesting/functionTests/tests/tools/SysinfoAPITest.java
> # commented out, see below
> # Skipping for 'SysinfoAPITest.java' due to comment: '// SysinfoAPITest
> currently fails when run against jars, so is' in
> java/testing/org/apache/derbyTesting/functionTests/tests/tools/_Suite.java
> # Skipping for 'SysinfoAPITest.java' due to comment:
> '//suite.addTest(SysinfoAPITest.suite());' in
> java/testing/org/apache/derbyTesting/functionTests/tests/tools/_Suite.java
> # Abandoned tests?
> java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/XATest.java
> # 2 errors
> java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/BLOBTest.java
> # 0 failures, takes around 5 - 8 minutes
> java/testing/org/apache/derbyTesting/functionTests/tests/lang/DateTimeTest.java
> # 0 failures, no suite method
> java/testing/org/apache/derbyTesting/functionTests/tests/lang/LangProcedureTest.java
> # 2 failures, 2 errors
> java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/SuicideOfStreamingTest.java
> # requires manual run?
> Please comment on this issue if you have information regarding one of the
> mentioned tests.
> It is my impression that the following initial actions needs to be taken;
> 1) Fix and enable XATest. Failures related to DERBY-3319?
> 2) Enable BLOBTest. Might try to reduce the run time.
> 3) Enable DateTimeTest by creating a suite method and adding it to a _Suite
> class.
> 4) Investigate LangProcedureTest failures/errors.
> FYI, the script found tests by looking for files named '*Test.java' in the
> java/testing/org/apache/derbyTesting/functionTests directory. I have not
> checked if there are JUnit tests that don't follow the naming scheme. All the
> processing was done by searching the source code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
