Hi Willem, > -- Regards Sudip On Thu, Oct 1, 2020 at 1:16 PM Willem Vermin > <wver...@gmail.com> wrote: >> I was able to run xsnow in Xvfb, along with fvwm or gnome-shell. >> >> Clicking buttons only affect what you see on the screen, there is no >> specific output caused by button clicks. >> >> What I could do, is run xsnow in Xvfb and parse the messages from xsnow >> at startup and end, and check if they are as expected. Would that suffice? >> >> Btw, >> The current test, based on the output of >> xsnow -h >> is trivial, but it does ensure that all needed system libraries are in >> place.
As the bug report of Sudip clearly states, these tests are valuable, we do appreciate them. Even when marked superficial, they will block dependencies that break your package, so that's OK. Why we want packages to be marked superficial if they only do trivial testing is because we treat packages with autopkgtests special in the judgement for migration. Now a bit. During the freeze a lot more. This special treatment is based on the understanding that significant testing has a reasonable chance to prevent bugs in the package itself from migrating to testing. So, for now it's really the maintainer call. If you believe that you can test the package in such a way that there's a reasonable chance to catch (some) bugs, than the autopgktest doesn't need a superficial restriction. We're not asking for full coverage. Please, just keep your testing limited to superficial testing if it's not reasonable to do more, but mark it as such. Plug (although I don't know how to do it exactly): there's reports that one can also test GUIs via the accessibility bus. The great advantage of doing that is that one is also testing for accessibility, which is a great good IMHO. Maybe there's more to check in the responses from that bus. Paul
signature.asc
Description: OpenPGP digital signature
