OT: Looking for examples of badly written bug reports

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello everyone,
I'm working on beginner QA and Automation training curricula for a local hack school in Sofia (https://github.com/atodorov/QA-101). I'm looking for examples of badly written bug reports which students can read and discuss what information is missing from them (e.g. why are they badly written).

Bugs can be on any bug tracker, not necessarily bugzilla.redhat.org. Strong favor for Mozilla, Gnome or GitHub issues in particular. They only need to be publicly accessible.


If you have any such examples please send them to me.


Thanks,
Alex
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux