#64 Find JUnit tests automatically
Closed: migrated 3 years ago by dmoluguw. Opened 12 years ago by edewata.

Currently to run JUnit tests in CMake the test classes have to be listed explicitly as follows:

add_junit_test(test-pki-common
    CLASSPATH
        ${classes}
        ${CMAKE_JAVA_INCLUDE_PATH}
    TESTS
        com.netscape.certsrv.authentication.AuthTokenTest
        com.netscape.certsrv.request.AgentApprovalsTest
        com.netscape.cmscore.dbs.CertRecordListTest
        com.netscape.cmscore.dbs.DBRegistryTest
        com.netscape.cmscore.request.ExtAttrDynMapperTest
        com.netscape.cmscore.request.ExtDataHashtableTest
        com.netscape.cmscore.request.RequestQueueTest
        com.netscape.cmscore.request.RequestRecordTest
        com.netscape.cmscore.request.RequestTest
)

Since there can be many tests this can be a maintenance issue. There should be a way to find all tests automatically, similar to that in Ant:

find_junit_tests(tests
    INCLUDE "*Test.java"
)

add_junit_test(test-pki-common
    CLASSPATH
        ${classes}
        ${CMAKE_JAVA_INCLUDE_PATH}
    TESTS
        ${tests}
)

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/636

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata