cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6968) Reduce Unit Test Times Due to Schema Loading
Date Tue, 10 Jun 2014 22:47:01 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027164#comment-14027164
] 

Tyler Hobbs commented on CASSANDRA-6968:
----------------------------------------

[~lyubent] 7327 has committed, so you should be good to update this now.

> 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)

Mime
View raw message