Search results

...graphics drivers, as well as a wrap up report of Fedora 13 Beta validation testing, and several other items. Translation includes reports of activity around ...icipants engage in to help sustain the community (e.g., to what extent is 'testing' a collaborative activity across the Fedora Project?)''', and ...

== Release criteria & validation test update round-up == * Re-jigged the level of quite a lot of test cases in the validation matrix to properly reflect the criteria ...

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...

...tests. It is important to cleanly separate implementation details of the ''testing system'' from the ''test suite'' and its framework. It is also important to # The ''testing system'' SHOULD stage the tests on Fedora operating system appropriate for ...

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...

...event wiki is ready and determined that a nightly live ISO would work for testing | style="color: #8c4a4a" | jlaska: i'll have to think about it if the server content isn't self-explanatory ...

...eMySQLwithMariaDB]] looks significant but we do not currently have planned testing for MySQL * [[Features/KScreen]] may impact KDE validation in a small way ...

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images. ...

...ill be used as a basis for identifying areas for improvement for Fedora 14 testing. Any thoughts, big or small, are valuable. If someone already provided fe ...that have been reviewed and accepted by key stake holders really expedites testing by improving bug escalation time and uncertainty regarding user impact. In ...

...ted. Quality Assurance brings news on QA statistics efforts, localization testing using Nitrate, and work on the F14 boot menu and bootloader. In Design Tea ...s scripts and third party applications that use the XMLRPC API at the test server to make sure they continue to function properly. ...

...ch for autotest to automatically transfer all autoqa config files from the server to the client : Continue testing and merging of new koji-watcher ...

...greatly asssists in the process of filing feedback on packages in updates-testing via Bodhi. Translation reviews the upcoming Fedora 13 tasks in that area, ...validation. In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be ...

* signing server * signing server ...

...of the weekly QA team meetings, increasing grub timeout, and X.org server testing. Our issue finishes with Security Advisories for Fedora 11 and 12. We hope .../ref>. He also said he was planning a release sprint to revise the release validation test plans for the new release criteria. ...

...of the weekly QA team meetings, increasing grub timeout, and X.org server testing. Our issue finishes with Security Advisories for Fedora 11 and 12. We hope .../ref>. He also said he was planning a release sprint to revise the release validation test plans for the new release criteria. ...

# Finish testing [[Releases/30/ChangeSet| Fedora 30 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing. ...

# Finish testing [[Releases/31/ChangeSet| Fedora 31 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing. ...

# Finish testing [[Releases/32/ChangeSet| Fedora 32 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing. ...