On our last QA meeting Adam Williamson notified us that there would be an Anaconda hackfest at the next FUDCon and we should raise our concerns (if we had some) regarding AutoQA and the UI re-write. Well, I don't know much about anaconda testing inside AutoQA, I just know we execute some anaconda tests, that's all. But I decided to kick off the discussion and CC relevant people. >From what I know, we have two kind of anaconda tests inside AutoQA: 1. older rats_install test written by Will Woods and executed James Laska in the past 2. newer anaconda_storage, anaconda_checkbot and compose_tree written by Chris Lumens and James Laska I am not sure which of those tests provide important feedback to the anaconda team and whether they are being used at all. Can relevant people provide more details about it? Anaconda team, do you have some specific questions about AutoQA integration and the UI re-write? Will you want to change your tests inside AutoQA in response the new UI and need to have some information from us? I'll happy to answer them if I can. Also, if the test authors have some comments or recommendation about the new UI architecture in order to allow simple automated testing, please post them here. Thanks, Kamil _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
