[ https://issues.apache.org/jira/browse/CASSANDRA-14931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721661#comment-16721661 ]
Stefan Podkowinski commented on CASSANDRA-14931: ------------------------------------------------ Ok, so this is not primarily about running dtests for that particular version and see if they pass, or find possible regressions? Given the infrequent amount and nature of patches for 2.2, I'd be wondering if it's really worth adding in-jvm dtests for regression testing? But that doesn't seem to be the point here, as we want this as a requirement for running in-jvm upgrade tests to be implemented starting with CASSANDRA-14937? > Backport In-JVM dtests to 2.2, 3.0 and 3.11 > ------------------------------------------- > > Key: CASSANDRA-14931 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14931 > Project: Cassandra > Issue Type: Improvement > Components: Testing > Reporter: Benedict > Assignee: Benedict > Priority: Major > Fix For: 2.2.14, 3.0.18, 3.11.4 > > > The In-JVM dtests are of significant value, and much of the testing we are > exploring with it can easily be utilised on all presently maintained > versions. We should backport the functionality to at least 3.0.x and 3.11.x > - and perhaps even consider 2.2. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org