incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-374) Improve integration testing in blur-core
Date Sun, 14 Sep 2014 12:33:33 GMT

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

Tim Williams commented on BLUR-374:
-----------------------------------

I've pushed up a branch named after this issue to support discussion.  The idea is to start
breaking up BlurClusterTest into multiple classes, e.g.:

IntegrationTestSuite
- TermsTests
- FacetTests
- ShardFailoverTests
...

As we begin to migrate to having "Commands" back Blur classic, it'll be advantageous to have
nice classes with full test coverage of each of the calls so we can have more confidence the
conversion is acceptable.  

Thoughts?

> Improve integration testing in blur-core
> ----------------------------------------
>
>                 Key: BLUR-374
>                 URL: https://issues.apache.org/jira/browse/BLUR-374
>             Project: Apache Blur
>          Issue Type: Test
>          Components: Blur
>    Affects Versions: 0.2.4
>            Reporter: Tim Williams
>            Priority: Minor
>
> We should migrate BlurClusterTest to be an integration suite in the same style that the
console's ConsoleTestSuite so that we can break out logical groupings of integration tests
to make them more manageable.



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

Mime
View raw message