From Fedora Project Wiki
Line 7: Line 7:


* Test Case Add or Remove
* Test Case Add or Remove
* Why no test cases for "yum" - Noriko
* Why no test cases for "yum" - Noriko
* Merge test cases for cracklib and passwd. The result of running passwd is the result for both cracklib and passwd - Noriko
* Merge test cases for cracklib and passwd. The result of running passwd is the result for both cracklib and passwd - Noriko
* Different sections for testcases for Gnome, Fedora, KDE, Firefox etc....
* While testing with live iso we need to have few changes in test cases accordingly.
* While testing with live iso we need to have few changes in test cases accordingly.
   * Instead of running the command as root we need to do sudo.
   * Instead of running the command as root we need to do sudo.
Line 21: Line 21:
   * Strings those are translated in po but in English in the application.
   * Strings those are translated in po but in English in the application.
   * Strings which are in English and cannot be found directly in po files.
   * Strings which are in English and cannot be found directly in po files.
* Each application requires a tracker bug instead of different testers filing separate bugs - Noriko
* Bug template with FLTG in CC which automatically post new bug when created to let all members know - Noriko
*
*


=== Suggestion and feedbacks on Fedora 18 testing===
=== Suggestion and feedbacks on Fedora 18 testing===

Revision as of 09:45, 24 April 2013

Feedbacks from COMMUNITY

Suggestion and feedbacks on Fedora 19 testing

  • Test Case Add or Remove
  • Why no test cases for "yum" - Noriko
  • Merge test cases for cracklib and passwd. The result of running passwd is the result for both cracklib and passwd - Noriko
  • Different sections for testcases for Gnome, Fedora, KDE, Firefox etc....
  • While testing with live iso we need to have few changes in test cases accordingly.
 * Instead of running the command as root we need to do sudo.
 * Few packages of system-config-* are giving error messages.
  • Few testers are might be confused in some situations like 100% translated, but rendering issues are present
 * One common guideline should be provided to testers to determine under which circumstances they should fail a test case.
 * As this is only for l10n testing we should pass the test case if it is 100% translated. And provide some additional informations regarding rendering issue, etc as a comment.
  • Provide information in system-config-language that "the languages names must be in English" to avoid any confusions for the tester - Shankar
  • Provide information to select both native language and English while setting the system - Shankar
  • A procedure or guideline to be provided for testers on how to find certain strings like -
 * Strings those are translated in po but in English in the application.
 * Strings which are in English and cannot be found directly in po files.
  • Each application requires a tracker bug instead of different testers filing separate bugs - Noriko
  • Bug template with FLTG in CC which automatically post new bug when created to let all members know - Noriko

Suggestion and feedbacks on Fedora 18 testing

  • Good feedback on new layout for test cases - Tagoh, Noriko
  • Anaconda testing to be done no matter its stable or not - Noriko
  • Better to have testing of comps component along with anaconda on Installation test day - Noriko
  • Provide bug numbers along with the test case or package if its tagged as 'this is currently not ready to test' - Noriko
  • Communication of testing dates to be earlier.


Suggestion and feedbacks on Fedora 17 testing

  • Test review - Firstboot - noriko - 20 Apr 2012
  • Special ISO creation - noriko - 20 Apr 2012
  • Communication Few day Early - Roman - 11 Apr 2012
  • Test cases more descriptive - Noriko - 20 Apr 2012


Back to FLTG home page