Ewen Cheslack-Postava

:+1: I'm running into this writing some muckrake tests.

This refers to a lot of services that were specific to the particular tests, but this is a more general framework-level issue as well. We might want to provide a...

@granders I think we're closer now, but this isn't actually resolved. First the easy part: we still have the problem that the commands being used are muckrake specific. It's actually...

Here's another idea: create a class in ducktape, maybe called something like `ClusterNodeCleaner`, that just defines the one method for cleaning a node. The default implementation just `pass`es. Then, make...

There's probably a good solution to this somewhere in Jinja itself -- I'd dig around in their code (or example code) to see if there's a better approach for passing...

Not sure I understand why you should have this. This is pretty normal in unit test frameworks as well. `setUp()` is supposed to be test-agnostic, so it shouldn't depend on...

@granders They don't, but it doesn't really change anything. I just meant that if you were doing anything that requires a standard pattern in your test, but customization per test,...

Additionally, @gwenshap suggests and I agree it's a good idea: > If individual tests announce timeouts, we can add it to the output > "this test will finish in 600...

Works in conjunction with https://github.com/confluentinc/rest-utils/pull/90 and avoids `Address already in use` errors during tests due to `choosePort` not being a reliable way to select a random available port. Will probably...

@aragnon I'd suggest using the `kafka-topics` command to determine the current state of replicas for the `_schemas` topic (or whatever topic you are using if you changed the setting `kafkastore.topic`)....