Hello everyone, I thought it would be a good idea to present the plan we have for Toaster QA for 1.9. As the title suggests, our main concern will be to automate as many of the tests as we can, with an eye on integrating the work with our existing end-to-end automation project. To that effect, here is the order I would like to handle things:
Step 1: - Since we are dropping support for analysis mode (as per 7711<https://bugzilla.yoctoproject.org/show_bug.cgi?id=7711>), I feel the first step should be to adapt the existing UI tests to work with the new managed mode interface. Estimated time: 2 man-days Step 2: - Implement the suggestions the developers sent us last week, about creating builds automatically with Selenium. This is required as a first step to integrate with the E2E solution. Estimated time: 2.5 man-days - I foresee a possible problem here getting selenium to detect when a build completes, so any ideas will be appreciated. Step 3: - Automate the remaining UI tests (the ones for the new pages i.e: All recipes page, All machines page) - Estimated time: 3-4 man-days - Automate the new backend tests and integrate them with the UI build tests. Estimated time: 3-4 man-days Step 4: - Create and automate TCs for new features that are being added in 1.9 - this will be ongoing, as features are completed. I'd like to raise this as an open for today's conference call, if possible. Regards, Mihail
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
