On Wed, Nov 16, 2011 at 17:49, Chris Lumens <clumens@xxxxxxxxxx> wrote: > By FUDCon, I hope to have a large amount of the UI code done. I think > it will then be too late to talk about what we should do for making sure > the UI is testable. We'll have a lot of code that might need to be > redone. So if we can start talking about what we can do now, I can > build in whatever's needed. You're talking sort of automated UI testing, right? Sure, that should be handled well beforehan. I was really thinking about the traditional hands-on do-a-hundred-different-installed-each-and-every-hour way of testing :) Starting with "do we need to adapt our test cases" to "what parts are in a testable condition 1 month in advance of Alpha TC1 already". But we'll really jsut do whatever needs to be done during the FUDCon timeframe and that are better done in a face-to-face meeting. Probably no specific plan on what we work just everyone bringing his list of things he'd like to do/discuss/change/... :) > Then at FUDCon we can talk about how useful it is and what improvements > we could make. Of course, we can also talk about non-UI testing stuff. Exactly! >> So, what do you guys think? Good idea? Bad idea? How much time should >> we plan? Right now we figured half a day (~4h) would be nice. What >> works best for you folks, Fri/Sat/Sun Morning/Afternoon? What other >> important things should get done? > > Any time works fine for me. My FUDCon schedule is pretty flexible, > given that I'm driving down there and don't have any plans for giving > talks. Right now I scheduled 4h on Sunday morning (9AM-1PM, mandatory hot dog feast afterwards) for really a couple of reasons. But if someone has strong feelings against that time slot, we can still discuss this. PS. the "how to make the new anaconda UI testable" should probably be discussed in a different/new thread :) _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
