How can you possibly pass QA if you HAVEN'T TESTED IT!!!! Jumping in the discution = Kyle, the QA team does not test the feature, it investigates code to detect something not respecting coding guidelines, coding
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2060 Paul Poulain <paul.poulain@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul.poulain@biblibre.com --- Comment #22 from Paul Poulain <paul.poulain@biblibre.com> --- (In reply to comment #16) practices. Sometimes, the QAer also find some possible side effect. Something that is not in the test plan, but could break another thing. In this case, there are 2 possibilities: * the QAer test itself * the QAer ask for more tests & switch back to "need signoff" * the QAer passes QA, warning the RM, that has the final cut anyway (yes, that's 3 and not 2, but it's friday, so it's permitted) ;-) Time to leave for me now, i'll test this patch lated & deeply -- You are receiving this mail because: You are watching all bug changes.