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.
Originally reported by mdrob, imported from: Consolidate test code
- status: Open
- priority: Major
- resolution: Unresolved
- imported: 2025-01-21
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.
Originally reported by mdrob, imported from: Consolidate test code