I've not been talking about this a whole lot but I've been working on a slightly different take on test automation as of late. The system as a whole is very rough and nowhere near complete but I think it does demonstrate several of the ideas I'm interested in from a high level.
I wrote several blog posts describing what I'd like to do: http://tirfa.com/down-with-test-automation-long-live-task-automation.html http://tirfa.com/an-initial-idea-for-taskbot.html http://tirfa.com/how-is-taskbot-different-from-autoqa.html I have my proof-of-concept demo running on my local systems: http://taskbot.tirfa.net Before spending a bunch more time on this, I want to see what the general thoughts were on the approach. - Does the general concept make sense for Fedora? - Is this something we should pursue? If so, I think that some of the next steps should be: - move the code somewhere so that others can contribute - migrate the proof-of-concept system to either autoqa-stg or fedora cloud systems (95% of the setup is ansible-ized so migration isn't too painful) - polish the bits that are there so that they actually do most of the things I'm talking about - do some investigation to be somewhat sure that we're not ignoring existing tools (autotest is first on my list, beaker is probably worth exploring a bit) Thoughts? Tim
signature.asc
Description: PGP signature
_______________________________________________ qa-devel mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/qa-devel
