Adam Williamson wrote:
> The other problem with screenshot validation is that it's inherently
> unsuited to some tests that are important to Fedora and that we have
> more-or-less working *right now* in AutoQA - things like depcheck and
> repoclosure - because all it can really tell you is 'does this results
> screen look like a known pass case'
Well, the test could:
1. bring up a known terminal emulator,
2. type this into it:
su -c "yum -y install packagename >/dev/null 2>/dev/null; echo $?"
3. have a PASS screenshot where the terminal emulator displays 0 and a FAIL
screenshot where the terminal emulator displays 1.
(But of course that takes a lot more work to set up than just checking the
dependencies directly.)
> - it's inherently pass/fail based, which is no use if the output you want
> is "these five dependencies are broken".
And this is of course the drawback of such an approach.
Kevin Kofler
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
