> SRPMs should be providing either:
> - include a standardized test section similar to DEB autopkgtest ("in-build"
> tests)
I realize "%check" is what's meant to be used for testing, but maybe its too
primitive or not enough? Or people are just too lazy to use it :)
--
test mailing list
What is the long term plan for package automated testing?
https://fedoraproject.org/wiki/Category:Test_Cases
E.g. 18264 packages * 20 tests run continuously by humans is a lot work. The
first question I expect many package maintainers to raise is that its a much
better investment to maintain
==
#fedora-meeting: Fedora QA meeting
==
Meeting started by coremodule at 15:01:14 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2016-07-18/fedora-qa.2016-07-18-15.01.log.html
.
Meeting
Missing expected images:
Kde live i386
Kde live x86_64
Cloud_base raw-xz x86_64
Cloud_base raw-xz i386
Atomic raw-xz x86_64
Kde raw-xz armhfp
Minimal raw-xz armhfp
Failed openQA tests: 28/80 (x86_64), 16/16 (i386)
ID: 25535 Test: x86_64 Everything-boot-iso install_default@uefi
URL:
# Fedora Quality Assurance Meeting
# Date: 2016-07-18
# Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
Sorry for the late notice, but we will be having the QA meeting this morning to
catch up on some
On 07/13/2016 01:29 AM, Adam Williamson wrote:
pschindl has done those when I've been away before, so he might be OK
with picking it up again, or if anyone else would like to try that's
fine. We'd only need a compose request if there's something we want to
test that requires a compose but
