m (Anipeter moved page FLTG CHECKLIST to FLTG CHECK-LIST: forgot to add '-' in the word "check-list")
Revision as of 09:09, 3 January 2013
Check-list for FLTG Members
1. Decide the date for all three testing - i18n testing day (by i18n team), l10n testing day and L10n/i18n Installation testing day based on the current release schedule.
2. According to the dates decided file a ticket on Fedora QA for the l10n test day.
3. Send an email to the release-engineering team with the ticket number, with a request to prepare the ISO and get it ready by a convenient date (at least 3 days before testing day).
4. Review both FUA and non-FUA test cases and :
(i) Make necessary changes to the existing test cases.
(ii) Add new test cases for the new packages or features added in the release.
5. Send the test cases to fltg mailing list for feedback.
6. Provide necessary details like, ISO link, test cases link, package links etc and correct information about the test days on the FLTG wiki page.
7. Send a test day notification email with FLTG page link to all mailing lists about the test days dates for the testers to be ready.
8. Send information on common bugs or issues to the mailing lists (fltg and trans), thus making the testers aware of the known issues.
9. Follow up with the release engineering team on the ticket for ISO.
10. Once ISO is ready, download and test the same.
11. Send another email to the mailing lists on test days about 2 days before the test day and a final reminder on the previous day.
12. Be present on the test day on the fedora-fltg irc channel to assist other testers.
13. The testing will be open for a maximum of 2-3 weeks. After 2-3 weeks send the testing report to the mailing list
14. Collect feedback from all the testers on the test day.
Tasks for FLTG Members
Based on the above listed check-list, the tasks for FLTG members towards the testing events can be divided as below:
1. Communications and different correspondences with various mailing lists.
2. ISO related tasks - includes filing ticket, send email to release-engineering team, follow up and testing the ISO.
3. Review of test cases - remove those irrelevant, add new test cases based on new features and packages.
4. Testing of the new test cases and provide feedback on certain common and known issues to the testers.
5. Assist all the testers on the test day.
6. Prepare report on the test day and send it to mailing list.
7. Collect feedback or testing and list them on the wiki page for future reference and further improvements.
The above tasks are shared among the members and are executed responsibly.