[
https://issues.apache.org/jira/browse/DAFFODIL-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678411#comment-17678411
]
Steve Lawrence commented on DAFFODIL-2772:
------------------------------------------
{quote}I would like to eliminate the creation of the scaladoc/javadoc, jars,
etc. as part of building the CLI also, as there is no point in waiting for that
to run the basic set of CLI tests. {quote}
The scaladoc/javadoc jars are created as part of the stage task, which is
needed for CLI tests that fork. Though, I *think* the only ones that actually
fork are in the TestCLIUdf suite because they change the classpath, which can
only be done by forking. So those would stay in the IntegrationTest
configuration.
And those UDF tests are where a good chunk of the time is spent in the
integration tests right now (forking is apparently very slow). Excluding the
UDF's, the integration tests take about about 65 seconds for me. The UDF tests
take 50 seconds. So by making this change, we only add about a minute to sbt
test (which for me is about 4.5 minutes), which is probably worth the ease of
use.
> Eliminate CLI it:test target and src/it directory in favor of ordinary
> src/test
> -------------------------------------------------------------------------------
>
> Key: DAFFODIL-2772
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2772
> Project: Daffodil
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: 3.4.0
> Reporter: Mike Beckerle
> Priority: Major
>
> Our CLI integration tests run much faster now.
> The reason for this separate 'sbt it:test' thing are gone.
> Having a separate src/it directory causes trouble for tooling. E.g., I find I
> have to rename any existing src/test directory to src/test1, then rename
> src/it to src/test in order to run the CLI tests from the normal JUnit type
> IDE support features. This is too clumsy.
> We should switch back to just having the CLI tests live in src/test and have
> them run the ordinary way via 'sbt test'. After all there's only 267 of them,
> whereas there are 4000+ tests in the regular daffodil 'sbt test' suite.
> I would like to eliminate the creation of the scaladoc/javadoc, jars, etc. as
> part of building the CLI also, as there is no point in waiting for that to
> run the basic set of CLI tests.
> If there are CLI tests which really depend on being able to fork and exec an
> executable, those can stay under src/it, but I think the vast bulk of the CLI
> tests should just become regular src/test/scala tests which are far easier to
> run.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
