Geoff
Geoff
per @benstopford: As a developer I want to be able to run groups of tests that I think are relevant to my change So that I don't have to wait...
This should happen after the basic framework has congealed a bit more.
There is only a method for copying between test driver and workers. It is also useful to be able to copy between worker nodes directly
When looking at logs, it's useful to immediately know the value of the timeout without having to refer back to the source code.
This will make it possible for sub-packages to use template files without having to duplicate template files within subpackages. I ran into this issue while creating a sub-package to hold...
A funky pattern has started to develop in kafka system tests, which means that `setup` isn't quite doing its job: - parametrized tests allow for exploding a single test method...
Refactoring a field into a property can lead to surprising results when rendering ``` class C(TemplateRenderer): x = 2 class D(TemplateRenderer): @property def x(self): return 2 c = C() d...
We can possibly make this pluggable in the future, but `git` awareness is a reasonable starting point if we're going to be aware of a vcs It would be useful...
One pain point in digging through logs is uncertainty whether, and by how much, the local time of various vms differ. Before each test run, it would be useful to...
Currently, error messages propagated from subclasses of BackgroundThreadService can be somewhat cryptic. Including the stacktrace if possible would be helpful