From Fedora Project Wiki

  • ...'21:00'' UTC (8am -> 5pm EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa]) === What to test? ===
    5 KB (628 words) - 21:17, 26 June 2015
  • * [https://www.redhat.com/archives/fedora-test-list/2009-December/msg00250.html Proposed meeting agenda] * jlaska to post recommendations on F-12 QA retrospective
    23 KB (2,860 words) - 09:00, 18 September 2016
  • === What to test? === The topic of this Fedora Test Day will be printing. We are interesting in the problems you face when usin
    5 KB (751 words) - 19:42, 26 June 2015
  • ..., we cover the activities of the QA team<ref>http://fedoraproject.org/wiki/QA</ref>. === Test Days ===
    18 KB (2,789 words) - 17:23, 6 July 2009
  • ...ting documentation on the wiki ([[QA/ReleaseCriteria)]] to assist triagers/QA in identifying and adding blockers to the Blocker List. This will be a collaborative effort with QA.
    37 KB (4,178 words) - 07:53, 18 September 2016
  • * [https://www.redhat.com/archives/fedora-test-list/2009-September/msg00444.html Proposed meeting agenda] = Upcoming QA events =
    58 KB (6,814 words) - 19:32, 21 September 2009
  • [https://www.redhat.com/archives/fedora-test-list/2009-July/msg00004.html Proposed meeting agenda] * [jlaska] - update [[QA/Goals]] wiki document
    46 KB (5,575 words) - 08:57, 18 September 2016
  • * jlaska+wwoods confirmed that things were on track for enabling automated test results sent to autoqa-results by F-11-GA ...e are known blocker bugs. Jlaska agreed, but noted it's difficult to plan QA time for testing the RC without specifics.
    58 KB (6,789 words) - 08:56, 18 September 2016
  • == How To Test == ...do for testing is OK, but it's much better to document what *I* can do to test your feature.
    6 KB (1,076 words) - 21:27, 7 October 2009
  • == QA Briefing == James Laska gave a briefing on QA efforts during F11, and planned objectives for F12 and beyond.
    57 KB (7,662 words) - 08:25, 18 September 2016
  • ...'21:00'' UTC (8am -> 5pm EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa]) == What to test? ==
    4 KB (627 words) - 19:29, 26 June 2015
  • * comphappy will email fedora-test-list with the link for the metrics beta and where to address bug reports. ...so far) * Should NEW triagers be asked to do NEEDINFO updates in 30 and 60 days if needed, or should this be left to triagers following the NEEDINFO chec
    63 KB (7,321 words) - 07:53, 18 September 2016
  • # Test the new desktop environment to ensure it works and integrates properly with == Test Plan ==
    3 KB (423 words) - 22:32, 28 June 2009
  • ...yle="color: #488888" | f13, there hasn't been an updated anaconda in a few days. maybe worth pinging the anaconda team about first? ...07a40" | I dont' know if there have been that many commits in the last few days
    42 KB (4,870 words) - 20:02, 4 May 2009
  • * [https://www.redhat.com/archives/fedora-test-list/2009-November/msg00043.html Proposed meeting agenda] See [[QA/Meetings/20091026#Action_items]]
    29 KB (3,780 words) - 08:59, 18 September 2016
  • [https://www.redhat.com/archives/fedora-test-list/2009-June/msg00652.html Proposed meeting agenda] * [jlaska] - update [[QA/Goals]] wiki document
    61 KB (7,189 words) - 08:57, 18 September 2016
  • ...ng package reviews, promotion at events / spreading the word about Fedora, QA, etc.) ...related efforts both up- and downstream (RDO, Packstack, Puppet-OpenStack, QA)
    6 KB (819 words) - 12:25, 19 September 2016
  • === What to test? === The topic of this Fedora Test Day will be sharing of various things over the network. This includes files
    6 KB (862 words) - 19:29, 26 June 2015
  • | name = Upgrade Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]
    9 KB (1,311 words) - 11:48, 17 April 2023
  • [https://www.redhat.com/archives/fedora-test-list/2009-August/msg00031.html Proposed meeting agenda] #* Sent ... see https://www.redhat.com/archives/fedora-test-list/2009-July/msg00655.html
    65 KB (8,005 words) - 08:58, 18 September 2016
View ( | ) (20 | 50 | 100 | 250 | 500)