Gang, I finally got some work done on the CI task for Taskotron in Taskotron. The idea here is that after each commit (of a relevant project - trigger, execdb, resultsdb, libtaskotron) to pagure, we will run the whole stack in docker containers, and execute a known "phony" task, to see whether it all goes fine.
The way I devised is that I'll build a 'testsuite' container based on the Trigger, and instead of running the fedmsg hub, I'll just use the CLI to "replay" what would happen on a known, predefined fedmsg. The testsuite will then watch execdb and resultsdb, whether everything went fine. It is not at all finished, but I started hacking on it here: https://pagure.io/taskotron/task-taskotron-ci I hope to finish it (to a point where it runs the phony task) till the end of the week. At that point, I'd be glad for any actual, sensible task ideas to ideally test as much of the capabilities of the libtaskotron/execdb/resultsdb as possible. The only problem with this kind of testing is, that we still don't really have a good way to test trigger, as it is tied to external events. My idea here was that I could add something like wiki edit consumer, and trigger tasks off of that, making that one "triggering" edit from inside the testsuite. But As it's almost 4am here, I'm not sure it is the best idea. Once again, I'll be glad for any input/ideas/evil laughter. Joza
_______________________________________________ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
