[
https://issues.apache.org/jira/browse/CASSANDRA-15539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-15539:
--------------------------------------
Description:
Extract in-jvm DTest _API_ and tests into a separate repository that is shared
between Cassandra branches. Tests themselves should be buildable using just
API, which is not the case now, since cluster creation relies on impl package,
since we do not have factories / constructors in API.
Main goals we’re trying to achieve:
1. We should be able to fail a build on API incompatibility between versions
2. Make it as easy as possible to detect break APIs between versions.
3. Make development of _tests_ based on in-jvm framework simpler
4. Reduce surface area of impact when making modifications to tests
Potentially, we’d also like to use a plugin to detect API incompatibilities
between in-jvm DTest API and in-branch implementations, and start running tests
using shared in-jvm test repository with each existing implementation in the
branch. This entails both running tests for all branches whenever there’s a
change in tests jar and running tests for a specific branch whenever the branch
has changed.
was:
Extract in-jvm DTest _API_ and tests into a separate repository that is shared
between Cassandra branches. Tests themselves should be buildable using just
API, wwhich is not the case now, since cluster creation relies on impl
package, since we do not have factories / constructors in API.
Main goals we’re trying to achieve:
1. We should be able to fail a build on API incompatibility between versions
2. Make it as easy as possible to detect break APIs between versions.
3. Make development of _tests_ based on in-jvm framework simpler
4. Reduce surface area of impact when making modifications to tests
Potentially, we’d also like to use a plugin to detect API incompatibilities
between in-jvm DTest API and in-branch implementations, and start running tests
using shared in-jvm test repository with each existing implementation in the
branch. This entails both running tests for all branches whenever there’s a
change in tests jar and running tests for a specific branch whenever the branch
has changed.
> Extract in-jvm API and tests out of Cassandra and into a separate repository
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-15539
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15539
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: Normal
>
> Extract in-jvm DTest _API_ and tests into a separate repository that is
> shared between Cassandra branches. Tests themselves should be buildable using
> just API, which is not the case now, since cluster creation relies on impl
> package, since we do not have factories / constructors in API.
> Main goals we’re trying to achieve:
> 1. We should be able to fail a build on API incompatibility between versions
> 2. Make it as easy as possible to detect break APIs between versions.
> 3. Make development of _tests_ based on in-jvm framework simpler
> 4. Reduce surface area of impact when making modifications to tests
> Potentially, we’d also like to use a plugin to detect API incompatibilities
> between in-jvm DTest API and in-branch implementations, and start running
> tests using shared in-jvm test repository with each existing implementation
> in the branch. This entails both running tests for all branches whenever
> there’s a change in tests jar and running tests for a specific branch
> whenever the branch has changed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
