Henry Robinson commented on ZOOKEEPER-725:

These are all excellent ideas - thanks for getting the ball rolling!

Some general questions to spur discussion:

1. There are a lot of tests in ZooKeeper, and it seems we'll have to rewrite 
most of them as part of this JIRA. Will it make sense to stage the rewrite 
process, maybe package by package or even finer grained? In general there's a 
dependency problem to be solved here, it would be good to figure out the 
details up front. 
2. How will we validate the new tests?
3. One particular facility that we sorely need is the ability to 
deterministically execute certain interleavings of concurrent processes (e.g. 
two leader election protocols) - this would help us perform validation of 
protocols to their specification. It seems Mockito would also help us here - is 
it sensible to expand its use beyond the client API?
4. I would also like to see a suite of stress tests built against each major 
component - is that beyond the scope of the JIRA?



> Test organization, methodology, and infrastructure improvements 
> ----------------------------------------------------------------
>                 Key: ZOOKEEPER-725
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-725
>             Project: Zookeeper
>          Issue Type: Test
>          Components: build, tests
>            Reporter: Konstantin Boudnik
> This is an umbrella feature for a number of improvements needed to happen in 
> ZK test realm

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to