You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Wojtek (Jira)" <se...@james.apache.org> on 2023/01/20 18:24:00 UTC

[jira] [Created] (JAMES-3879) Use jUnit Category/Tag to exclude by default integration/long running tests

Wojtek created JAMES-3879:
-----------------------------

             Summary: Use jUnit Category/Tag to exclude by default integration/long running tests
                 Key: JAMES-3879
                 URL: https://issues.apache.org/jira/browse/JAMES-3879
             Project: James Server
          Issue Type: Test
    Affects Versions: master
            Reporter: Wojtek


On the main James page (https://github.com/apache/james-project#how-to-check-the-compilation) there is a text:
"Useful (maven) options includes: `-DskipTests` to skip the long to execute resource consuming test suite that requires a docker daemon."

I propose using `Tag` annotation to mark those test ("docker", "slow", "integration", etc.) and by default exclude those categories.

Main benefit, that majority of tests would be run when building James either way (thus, allowing to test most of the code) and integration tests can still be run (either locally or on CI)




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org