On Mon, 2014-09-29 at 20:41 -0500, Michael Catanzaro wrote:
"All applications installed by default in Fedora Workstation
with each MUST and MUST NOT guideline in the Applications and Launchers
policy."  (This is already mentioned at the very bottom of the
So Beta TC1 request is filed now, and I'd like to get the criteria in
place (and then test cases) ASAP. I'm therefore proposing to make this a
Beta criterion tomorrow or so if no objections are filed. (We can always
adjust later). We can then write a test case for it.
On Mon, 2014-09-29 at 17:27 -0700, Adam Williamson wrote:
> We don't really have criteria relating to a11y or complex input methods;
> this isn't Workstation-y in particular, but something that might be
a11y is a good target not just for release criteria, because it is
absolutely essential for a few users, but also for a test plan, since an
a11y regression is quite likely to be missed by developers.
I'd just want to be sure we're actually in shape to enforce any
requirements we decide to set. If anyone has a realistic criterion / set
of criteria for a11y stuff they'd like to propose, we can certainly look
at including that. This has to be stuff we can *actually stand behind*
for F21 Beta / Final (as appropriate).
It's generally expected that all release criteria are backed by test
cases, there are conventions/templates for both associating criteria
with test cases (the References sub-note for all criteria is expected to
cite at least one associated test case) and test cases with criteria
(test cases that enforce release criteria are expected to include a
template which produces an admon/info notice explaining which release
criterion they enforce, see
So, I'd certainly be intending that we create test cases (or
appropriately extend existing ones with the template and categorization,
where they exist) for any criteria we add.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net