That sort of testing - just running the app, and checking that various features work - is a perfectly fine test plan (ideally describing *what* features to test). We don't necessarily require¹ evidence of testing - if you say you've tested it, that's generally good enough.
What we *do* want is the detail of the version tested, because it's easy to accidentally test the wrong thing. Which is why we ask for the version of the package tested in a verification report. Although, for this specific case, testing in an LXD container might be insufficient, as the kernel's apparmor implementation might be relevant. ¹: Although for bugs where there's a really clear way of demonstrating the bug with terminal output that makes both the test case and verification easier! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2120284 Title: [SRU] Tellico AppArmor policy parser error: unexpected TOK_ID, expecting TOK_MODE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marble/+bug/2120284/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
