You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Lyuben Todorov (JIRA)" <ji...@apache.org> on 2014/06/01 22:43:01 UTC

[jira] [Updated] (CASSANDRA-6968) Reduce Unit Test Times Due to Schema Loading

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

Lyuben Todorov updated CASSANDRA-6968:
--------------------------------------

    Attachment: trunk-6968-speedup-unittests.patch

> Reduce Unit Test Times Due to Schema Loading
> --------------------------------------------
>
>                 Key: CASSANDRA-6968
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6968
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tests
>            Reporter: Tyler Hobbs
>            Assignee: Lyuben Todorov
>            Priority: Minor
>             Fix For: 2.1.1
>
>         Attachments: trunk-6968-speedup-unittests.patch
>
>
> Unit tests which extend SchemaLoader take about 6s longer to run than the others, on average.  We could greatly reduce the time it takes to run the tests by improving this.
> None of the tests require everything that SchemaLoader does.  We should change SchemaLoader into a set of test utilities that are run as needed in {{\@BeforeClass}} and {{\@AfterClass}} methods.  Additionally, instead of running a full cleanup, most tests could simply use a keyspace or column family with a unique name (class/method name or perhaps class/method name + timestamp).



--
This message was sent by Atlassian JIRA
(v6.2#6252)