On Thu, Dec 26, 2013 at 07:52:04PM -0800, Adam Williamson wrote: > No. There's a bad one, which is AutoQA. The problem with it is it's more > or less considered obsolete now as far as new development goes; the devs > are working on Taskotron to replace it, but I don't believe it's ready > for test contributions yet, unfortunately. > > Once we have Taskotron up and going (which I believe is aimed for the > first half of 2014), we can start adding more automated tests, which > we'd very much like to do, but I don't think anyone's keen on adding > extra tests to AutoQA at this point, as any time spent implementing them > and keeping them working takes away from time spent developing > Taskotron. Please can I *urge* the Taskotron developers to fix the major deficiency with AutoQA: Allow package maintainers to flexibly upload tests to run on their package. Ideally these tests would be contained in dist-git; for example Taskotron could look in the current branch for a 'test.sh' file and run it. Thus allowing the developer to associate tests with the package, have them run after a build, and be able to change/disable the tests at any time. (I did read the Taskotron wiki page before posting this .. I could not see any place where this AutoQA shortcoming would be fixed, but my apologies if this is already planned) Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
