On Sat, 2010-02-27 at 11:41 +0100, Till Maas wrote:
> Ok, maybe the question should be then: How much does AutoQA support me
> writing these tests? E.g. this test is pretty simple, but afaics there
> is no easy support for the common tasks that are needed to run the test,
> but not really part of the test, e.g. installing the package or setting
> up a machine.
>
> The Writeing AutoQA Tests wiki page[0] says:
> | I'll say it again: Write the test first. The tests don't require
> | anything from autotest or autoqa. You should have a working test before
> | you even start thinking about AutoQA
>
> But this is not really supportive, because if I want to test a packages,
> I need a framework that creates the initial environment, e.g. a system
> of the Fedora version to be tested with the package installed and there
> needs to be a way to interact with the programs.
>
> Or is this really a test I can easily integrate into AutoQA currently?
> Say we start without locales and commandline arguments, then the test
> would be:
>
> Input: Package to be tested as ${PACKAGE}
> for binary in $(rpm -ql ${PACKAGE} | grep bin); do ${binary} 2>&1 | grep
> "Segmentation fault" && echo "test failed" ; done
It'd probably be best to ask on the autoqa-devel mailing list - you'll
get Will and Kamil there, who know far more in detail than I do :)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
