[jira] [Commented] (DAFFODIL-2811) sbt IntegrationTest being deprecated, need alternative for slow CLI tests

["Steve Lawrence (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DAFFODIL-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720485#comment-17720485 ] 

Steve Lawrence commented on DAFFODIL-2811:
------------------------------------------

RC2 has been released, and the release notes include a suggestion for migration away:

https://eed3si9n.com/sbt-1.9.0-beta#deprecation-of-integrationtest-configuration

Based on that, which I think meets all the requirements listed above, we could create a "daffodil-test-integration" subproject which is not published or aggregated, and move all slow forking CLI tests into that project. Any other slow tests can be move there as well if we detect them. IDE's can be configured to ignore this subproject if they do not want to run these tests, but can run them just like any other test. Our CI would be modified to run "sbt daffodil-test-integration/test" instead of "sbt IntegrationTest/test". And we can configure the subproject to disable parallelized tests.

> sbt IntegrationTest being deprecated, need alternative for slow CLI tests
> -------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2811
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2811
>             Project: Daffodil
>          Issue Type: Bug
>          Components: CLI
>            Reporter: Steve Lawrence
>            Priority: Minor
>
> SBT 1.9.0 is planning on deprecating the IntegrationTest configuration:
> https://eed3si9n.com/sbt-1.9.0-beta
> We currently use this config for slow running CLI tests that fork. With the upcoming release of 1.9.0, we may want to consider an alternative. Some requirements for the alternative:
> * Should allow running the tests in an IDE, which is currently difficult/impossible since not all IDE's support the IntegrationTest config
> * The CLI integration tests depend on the "daffodil-cli/stage" task since they actually execute the binary. Whatever alternative we choose should not run that task unless integration tests are actually run since staging the CLI can take awhile. We don't want to slow down the normal test cycle
> * We need the ability to disable parallelization when running these tests, otherwise we can quickly run out of memory on systems with limited resources (e.g. GitHub actions)
> * The tests should not run by default when running "sbt test". They are expensive and time consuming and usually don't need to be run as frequently as normal tests.



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