Hi, I agree with Paul that we need a clear description to be able to test a big feature like this: - does it add new system preferences? - new options in other configuration parameters? - does it need a cronjob? - does it introduce new requirements? - which modules/parts of Koha might be affected by those changes? - ... Additionally, we need information about test cases. But ideally people should not only test those, but think about it and test a bit more. To come up with a complete test plan for big features is very hard. I think it's a plus that this branch is already used in production, but it still needs testing. One library might not use all features or have figured out a setup that works, while variations of this configuration might not. I think we could use a wiki page here, where people can see what to do and how to test, add comments about what they tested, additional test cases etc. For other smaller bugs I would like to see the test plans included in the commit message. So the most recent patch should have all the information I need for testing. -- Katrin
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Paul Poulain Sent: Wednesday, November 30, 2011 10:15 AM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] Testing patches with a lot of comments
Hello koha-devel,
I sometimes face patches that have a lot of comments, more than one patch, and it's not always easy to understand how to test the proposed patches. We need the following things to be very clearly explained: * test case / step to reproduce * which patch(es) to apply (* anything else ?)
Does anyone see a way to have those points clearly displayed/described in the bug ?
For example, look at bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5549, about hourly loans = 33 comments, it has only 2 small patches, it's clear more things are needed, maybe the git repo in comment 1. Or is it the one in comment 3? which repo does comment 6 use ? Maybe it's comment 25 in fact. Anyway, it's quite unclear, and, even with all my willingness, I don't know how/what to test.
I took this example just because Eliott rises this bug a few hours ago on this ML. But it's not a single case.
If anyone has a suggestion, it's welcomed !!! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/