On Fri, 2017-07-07 at 12:24 -0400, Matthew Miller wrote: > It seems like it would be useful if we could have a way to connect "I'm > making an update in bodhi!" back to "This update is likely to affect > a given release criteria". For example, it would be nice to have > something show up in bodhi noting that updates to Firefox might affect > https://fedoraproject.org/wiki/QA:Testcase_desktop_browser We can already link packages and test cases such that updates that include those packages will always list those test cases: https://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation I believe there's possibly some kind of bug with the process of syncing the wiki categories into Bodhi at present, I'm not totally sure of the current status of that, but the mechanism is already there. > and even better, if that would also show up for updates to Firefox's > dependencies. This isn't done yet. (And honestly, doing it in a simple-minded way would be a bit tricky; do we really want, say, every update to glibc listing pretty much every package-linked test case that exists?) > The idea here is to help developers and packagers be more mindful of > the release criteria that their updates might impact. Does this sound > in theory desirable? Can you think of a way to do it other than listing > specific packages in the test cases? I know that there's some tension > between this and the generic broad expression used for many test cases. There really wouldn't be any 'tension' in adding the browser test case to the firefox package categories, so we could just go ahead and do that. Establishing links to *release criteria* - which is what you keep saying, but then your example involves a test case and not a release criterion, which confuses me a bit - is harder, because we don't really have any representation of the release criteria which is easy to interact with programmatically... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
