On 02/01/2011 10:47 AM, Kamil Paral wrote:
Are/were there any specific plans for tools? (py.test, unittest, nose, dingus ...)
To tell the truth, I have no experience with unittesting in Python and thus I don't even know the frameworks. If you decide to work on that, it's your call.
mkrizek originally created a single directory containing unittest files. But there are also some other tests contained in several other python files in our project (check out the executable files and their main methods). I don't know if it is better to execute them directly, or move the unittest code into the common directory. Again, depends on your judgement.
OK, I have some ideas but I want to make sure that they are appropriate for AutoQA before I go much farther with them. I'll make a proposal before I go too far, though.
Do we have any requirements on where AutoQA will run? Specifically, I am wondering about older versions of Fedora or any version of RHEL. I don't think that all of the tools I'm thinking of are currently in any repositories and I don't want to head down that path if it is already a dead end.
I realize that I would have to package any new tools, have them approved and at least in rawhide before having a chance of getting anything in master.
Thanks,
Tim