On Thu, Jan 12, 2017 at 4:32 PM, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > Hi folks! So I finally got around to that 'think about USB test > coverage' item that's been on my todo list forever. > > I propose we add a table to the Installation Validation page. The > purpose is simply to check that writing images is working with > mediawriter in the major supported environments: Windows, macOS , and > the supported stable Fedora releases. So it could just look like this: > > > Windows macOS Fedora 24 Fedora 25 > QA:Testcase_USB_fmw > > with the intent being that we at least check that writing any one > release blocking image with mediawriter in each environment. > > We could split Windows into 7, 8 and 10 or something, but not sure if > it's really necessary... > > Thoughts? Well I don't really want to eat a hat, because I've had my fill for a lifetime, but I'd eat my hat if FMW works on Windows 10 but does not work on Windows 7. Or vice versa. So may be ask mbriza which one to test on, and hope the numbers game fills in the rest on its own. The API/ABI stability on Windows is pretty extreme. In order of market share though, by a long shot it's Windows 7, then 10, and a distant third is 8.1 and then 8(.0) barely registers. So weirdly enough, chances are it'll work on 8/8.1 if it works on 7 and 10. So a thorough test would be testing both 7 and 10. Less thorough, but sane, is testing just on 10. (For those who don't know, it's possible to get a free copy of Windows Enterprise, the installer iSO will install a copy of Windows that'll work for 90 days, the timer starts from the time of installation; i.e. it's not the download ISO that's time limited.) FWIW at the moment on Fedora 25 I'm running into these two bugs and can't write images at all with FMW. https://bugzilla.redhat.com/show_bug.cgi?id=1412063 https://bugzilla.redhat.com/show_bug.cgi?id=1412057 -- Chris Murphy _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
