[
https://issues.apache.org/jira/browse/CASSANDRA-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832531#action_12832531
]
Gary Dusbabek commented on CASSANDRA-782:
-----------------------------------------
Two more things and I think we're done. First, I think that `ant clean` should
also delete ${test.reports}. Second, would you consider renaming
CassandraServiceDataCleanerTest to CassandraServiceTest? The reason being that
it doesn't really test any of the functionality in CassandraServiceDataCleaner.
(Or you could keep it named the same and add some tests to verify that
CassandraServiceDataCleaner does what it claims to do.)
> Create a cleanup utility that cleans all data directories
> ---------------------------------------------------------
>
> Key: CASSANDRA-782
> URL: https://issues.apache.org/jira/browse/CASSANDRA-782
> Project: Cassandra
> Issue Type: New Feature
> Components: Contrib
> Affects Versions: 0.6
> Reporter: Ran Tavory
> Assignee: Ran Tavory
> Priority: Minor
> Attachments: CASSANDRA-782.patch, CASSANDRA-782.patch
>
>
> A cleanup utility is useful for tests, unit tests of products that use
> cassandra as a blackbox.
> A cleanup utility may be used in conjunction with an embedded cassandra
> service (see CASSANDRA-740) in the following way:
> 1. Test starts by creating the data directories, if they don't exist, and
> deleting all content in them to make sure there's a fresh clean start (all
> this provided by this improvement)
> 2. Test starts an embedded cassandra service (provided by CASSANDRA-740).
> 3. Test runs... adds data to cassandra, reads, deletes etc.
> 4. Test stops the embedded cassandra service
> 5. Test cleans up all data to leave the file system clean.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
