accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2139) Create list of features which need manual verification
Date Mon, 06 Jan 2014 21:33:52 GMT

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

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

bq. The more testing we can automate the better

Bingo.

bq. What about bigtop, does anyone know what it offers? 

My (uneducated) presumption was that Bigtop would be more pain than it would be worth for
our use of it, but that's a painfully uneducated assertion. I know [~jvines@gmail.com] and
[~mdrob] have both done stuff with Bigtop, perhaps they could weigh in on how easy/hard this
would be. Ultimately, I don't want to be bogged down with a bunch of other things -- I just
want to write my Accumulo test and avoid the situation where I can't test what I want to test
due to limitations of the testing harness itself. We want to test Accumulo here, not test
Accumulo *and* it's functionality with everything else.

Ideally, I'd like to not have to worry about setting up things like Hadoop/ZooKeeper for such
a test, but leave them as a pre-req to provide fs.default.name/fs.defaultFS, the zk connection
string, and whatever necessary env variables we need to bootstrap Accumulo. 

I dunno -- if tool exists that provides us what we need without a bunch of other limitations,
we should use it.

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

Mime
View raw message