You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/01/06 21:39:54 UTC

[jira] [Commented] (ACCUMULO-2139) Create list of features which need manual verification

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

Josh Elser commented on ACCUMULO-2139:
--------------------------------------

Brainstorming, perhaps it would be a good idea to centralize some of the "real instance" tests that we have now (most importantly randomwalk and continuous-ingest) into a harness?

# Remove the duplication in setup for both of these tests and make it easier to add something new.
# Lower-barrier to entry in creation of distributed tests
# Introduce the notion of validation for the said test (would be easy for CI, but hard for RW).

This might also have the indirect perk of providing something that's reusable by users themselves? Not sure if there is worthwhile merit in another project that already exists here. My first though was that integration of some sort of process management library in a scripting language would be sufficient and much better over the shell scripting hack-together we have now. 

> Create list of features which need manual verification
> ------------------------------------------------------
>
>                 Key: ACCUMULO-2139
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2139
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Keith Turner
>             Fix For: 1.6.0
>
>
> If an issue like ACCUMULO-2036 can not be tested automatically, then maybe it should be added to a list of things that must be verified before release.   Where should this list go and what else should be on it?  
> Upgrade seems like another candidate for the list.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)