You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2015/09/22 21:21:04 UTC
[jira] [Commented] (CURATOR-232) Consolidate test code
[ https://issues.apache.org/jira/browse/CURATOR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903267#comment-14903267 ]
Jordan Zimmerman commented on CURATOR-232:
------------------------------------------
FYI - a new bug that just came in suggests that all recipes should be tested with standard clients and clients with namespaces.
> Consolidate test code
> ---------------------
>
> Key: CURATOR-232
> URL: https://issues.apache.org/jira/browse/CURATOR-232
> Project: Apache Curator
> Issue Type: Improvement
> Components: Tests
> Reporter: Mike Drob
>
> Writing additional tests for Curator can be fairly intimidating to new users, and it looks like things just get copy and pasted a lot. We can consolidate a lot of test code, starting with how we expose {{Timing}} and {{CuratorFramework}} objects. This is a probably going to be a longer term effort with several JIRAs, so I'm not concerned with this one issue covering absolutely everything, I just want to make new tests easier to write.
> One easy route is to make heavier use of annotations, like the {{@BeforeMethod}} and {{@AfterMethod}} instead of {{try/finally}} when making sure resources are cleaned up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)