You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Steve Lawrence (JIRA)" <ji...@apache.org> on 2018/03/06 18:14:00 UTC
[jira] [Resolved] (DAFFODIL-1911) Move daffodil-cli tests to use
sbt's "integration" test capabilities
[ https://issues.apache.org/jira/browse/DAFFODIL-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lawrence resolved DAFFODIL-1911.
--------------------------------------
Resolution: Fixed
Assignee: Steve Lawrence
Fixed in 4e23af5c2a2033967e2ea3fc662ffd567473a489
> Move daffodil-cli tests to use sbt's "integration" test capabilities
> --------------------------------------------------------------------
>
> Key: DAFFODIL-1911
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1911
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Steve Lawrence
> Assignee: Steve Lawrence
> Priority: Major
> Fix For: 2.1.0
>
>
> CLI tests take a long time to run, so by default we do not aggregate the daffodil-cli project so that they are no run when you run {{sbt test}}. However, this leads to some bad side effects (e.g. cli stuff not compiling by default, weird behaviors with sbt clean not cleaning daffodil-cli). We want to enable aggregation, but there's not way to disable the a single command (test) for a single subproject (daffodil-cli).
> However, SBT has an "integartion test" concept, where you can put tests in {{src/it/\{scala,java,resources}}} and they will only be run via {{sbt it}}. This would be a good way to reenable aggregation of daffodil-cli, but prevent CLI tests from running with {{sbt test}}. Need to confirm that this works as expected and that we can maintain the sbt debug capabilities
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)