[CASSANDRA-15539] Extract in-jvm API and tests out of Cassandra and into a separate repository

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.17, 3.0.21, 3.11.7, 4.0-alpha4, 4.0
• Component/s: Test/dtest/java
• Labels: pull-request-available
• Change Category: Quality Assurance
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/1f72cc6197187abac5b1f70a19589dd4883e8d98

Test and Documentation Plan

(described in jira text)

• Assignee: Alex Petrov
• Reporter: Alex Petrov

Authors

Alex Petrov

Reviewers

David Capwell, Dinesh Joshi

• Created: 31/Jan/20 12:59
• Updated: 16/Mar/22 13:08
• Resolved: 27/Mar/20 18:26

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.

Issue Links

• relates to: CASSANDRA-15683 Fix NPE in SimpleReadWriteTest after test framework behavior change
• links to: GitHub Pull Request #437
• links to: GitHub Pull Request #452
• links to: GitHub Pull Request #453
• links to: GitHub Pull Request #454