I think you have good core ideas (haha, the "core" word again:)), but the whole proposal seems a bit overkill. I'd personally suggest:
1. Use the "core apps" concept, but not cross-distro wide, but always specific to a particular Spin. The concept would mean "these apps must not be missing and are subject to higher quality standards [to be defined in
a generic fashion and decided on a per-case basis as usual]". The SIGs would need to back this idea, i.e. have an interest in this increased quality checking *and blocking*. It might happen that no SIG would want that due to resource constraints.
(This would still need some fine-tuning, because we have something similar in Server, but already present as individual criteria.)
2. Any time we feel there's an important app missing in a non-blocking spin, just file a bug, no bureaucracy.
3. Amend basic functionality criterion to say that application importance affects the level of standard we have when judging the basic functionality it the impact on the users. All while not lowering the bar for non-important
apps (even for those at least the basics must work).
I completely agree on these points with Kamil. I would just extend the first point by one thought/idea that Lukas already brought up:
We should increase the detail level of the specifications for the core apps. Instead of listing what apps should be used, we should additionally specify what tasks need to be handled by these apps. Based on this specification
we can write proper test cases that actually have a bi-directional-traceability (and therefore are based on a common source, the specification).
On 10/11/2018 05:09, pmkellly@xxxxxxxxxxxx wrote: [...]I think for just the Workstation testing I do myself I will continue with my "over testing" approach where I "try out" all of the graphical app's that anaconda installs. and file bugs (not nominated) for issues I fine.That's wonderful!I also see the point that the non-Gnome spins could benefit from some more testing and will start doing testing with one or two of them. Any suggestions on which spins could benefit most from some attention?Mate of course! Although, I admit I'm biased here... But more sensibly, I don't have sufficient knowledge to answer your question properly. [...] Cheers, Gavin _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=""> List Guidelines: https://eur02.safelinks.protection.outlook.com/?url=""> List Archives: https://eur02.safelinks.protection.outlook.com/?url="">
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
