Search results

<!-- Identify our current test workflows (or use cases)--> ...ists general use cases when using wiki and summarizes main test events use cases step by step.

<!-- Make sure the pages is named as "Test Day:YYYY-MM-DD topic" --> | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

== What to test? == Today's installment of Fedora Test Day will focus on:

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

For example: This change allows package upgrades to be performed automatically and rolled-back at will. Does this improve some specific package or set of packages?

...iver packages, and associated support code from the `xorg-x11-server-Xorg` package. ...ilverblue machines, this means running them from the host and not inside a toolbox.

| name = '''Kernel 6.6 Test Week''' | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

| name = '''Kernel 5.17 Test Week''' | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

| name = '''Kernel 5.15 Test Week''' | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

...it is unwanted for other queues, because it can be hard to read in larger cases. Please attach incident-bound journald log only when it is necessary. $ ipptool -tv <your_printer_device_uri> get-printer-attributes.test &> ipptool_log