On 02/07/2011 06:37 AM, James Laska wrote:
on using existing well established python test frameworks (nose or
unittest). My initial thought is we have enough hassles managing
content that is not yet packaged. I'd like to leverage existing
framework documentation/howto's where possible.
Don't worry, I'm not looking to cause too much trouble yet :)
I'm not sure that this discussion is going to be incredibly productive
without examples. I'll be working on that today
As far as RHEL requirements, nothing comes to mind immediately other
than ensuring python compatibility by way of pylint (or similar). We'll
likely need to maintain a systemd unit, as well as a SystemV initscript.
I'm not sure what unit tests would be required there. I'd like to see
more unit tests for each of the watchers to validate expected outputs
based on a controlled set of inputs. Since they inputs depend on online
services (repodata, koji and bodhi), crafting some known inputs will be
a fun exercise.
Yeah, I'm already running into that. I'm trying to figure out how I can
trigger stuff in AutoQA without touching outside services. I have some
ideas but again, not an incredibly productive discussion without examples.