You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2016/03/10 15:21:40 UTC

[jira] [Resolved] (CASSANDRA-5330) make it possible to run unittests in any order

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

Marcus Eriksson resolved CASSANDRA-5330.
----------------------------------------
    Resolution: Not A Problem

I think this has been fixed, otherwise it is not a big problem

> make it possible to run unittests in any order
> ----------------------------------------------
>
>                 Key: CASSANDRA-5330
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5330
>             Project: Cassandra
>          Issue Type: Test
>          Components: Testing
>            Reporter: Marcus Eriksson
>            Priority: Minor
>
> SchemaLoader does its thing @BeforeClass and @AfterClass, should ideally be done @Before and @After - otherwise tests will se leftovers from earlier unit tests
> guessing this caused most of the issues in CASSANDRA-5315



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)