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

["Dave Thompson (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Thompson closed DAFFODIL-2811.
-----------------------------------

Verified the specified commit (commit d524759ea7a7ec8e5eacee1614d3877df3d756ea) is included in the latest pull from the daffodil repository.

Verified, via review, changes identified in the commit comment were implemented. 

Verified file TestCLIUdfs.scala is no longer under daffodil-cli subproject and move to the new daffodil-test-integration subproject.
Verified the command sbt IntegrationTest/test no longer executes the udf test suite. 
Verified the command sbt daffodil-cli/it:test no longer executes the udf test suite. 
Verified the command sbt daffodil-test-integration/test now executes the udf test suite.

> 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, Infrastructure
>            Reporter: Steve Lawrence
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> 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)