From Fedora Project Wiki

  • * [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
  • ...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-November/msg00043.html Proposed meeting agenda] See [[QA/Meetings/20091026#Action_items]]
    29 KB (3,780 words) - 08:59, 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
  • [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
  • # Test the new desktop environment to ensure it works and integrates properly with == Test Plan ==
    3 KB (423 words) - 22:32, 28 June 2009
  • [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
  • * 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
  • === What to test? === Today's instalment of Fedora Test Day will focus on user experience issues of peripherals. We are interesting
    9 KB (1,337 words) - 19:40, 26 June 2015
  • ...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
  • | 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
  • ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) === What to test? ===
    7 KB (1,175 words) - 16:47, 9 January 2012
  • ...e.net/fedora-qa #fedora-qa] ([http://webchat.freenode.net/?channels=fedora-qa webirc]) == What to test? ==
    8 KB (1,128 words) - 21:32, 26 June 2015
  • * [https://www.redhat.com/archives/fedora-test-list/2009-September/msg00307.html Proposed meeting agenda] = Upcoming QA events =
    63 KB (7,431 words) - 08:59, 18 September 2016
  • [https://www.redhat.com/archives/fedora-test-list/2009-August/msg00242.html Proposed meeting agenda] == F-12-Alpha Test Compose ==
    69 KB (8,437 words) - 21:00, 10 August 2009
  • ...Oct 8, 2009 || ALL DAY || [irc://irc.freenode.net/fedora-test-day #fedora-test-day]) == What to test? ==
    10 KB (1,623 words) - 21:17, 26 June 2015
  • ...''0:00'' UTC (8am -> 8pm EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa]) === What to test? ===
    7 KB (1,057 words) - 19:33, 26 June 2015
  • ...'21:00'' UTC (8am -> 5pm EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa]) == What to test? ==
    9 KB (1,386 words) - 19:38, 26 June 2015
  • | style="color: #407a40" | The signature script and bug triage days | style="color: #407a40" | That is a idea that would work with bug triage days where we are all here
    36 KB (4,988 words) - 07:53, 18 September 2016
  • ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) = What to test? =
    5 KB (837 words) - 19:39, 26 June 2015
View ( | ) (20 | 50 | 100 | 250 | 500)