<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Strong agreement from me for "have the test plan in the commit
message." </p>
<p>Bugs in bugzilla do get messy, but as long as we are applying the
latest patch, the plans are always right there for you to look at.
Also for everyone else to look at. And immortalized in git. <br>
</p>
<p>Git. They go in git, and by extension, on the patches attached to
Bugzilla.<br>
</p>
<p>Cheers,<br>
Liz<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 04/10/17 19:55, Marc Véron wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b41b429a-0a7f-4a4f-bdb2-1b5cda5c6b4b@veron.ch">Hi David
<br>
<br>
I think it is a good practice to have the test plan as commit
comment and to obsolete any comments that are related to obsoleted
patches. In Bugzilla, comments can be obsoleted by entering the
keyword 'obsolete' as tag and then hit the return key.
<br>
<br>
Marc
<br>
<br>
<br>
Am 04.10.2017 um 01:56 schrieb David Cook:
<br>
<blockquote type="cite">
<br>
Hi all,
<br>
<br>
I’ve been wondering about the best place to put test plans. I
think traditionally we include them in our git commits, but I
feel like it would be better to include them as standalone
comments in Bugzilla.
<br>
<br>
My reasoning is that finding test plans can be really difficult
when you’re scrolling back through numerous autogenerated
per-commit comments. And if there is lots of rebasing or
modifications, you wind up with a million test plans, so you
can’t even Ctrl + F really.
<br>
<br>
I figure when a patch is ready for testing, the developer should
write 1 comment containing all test plan instructions and post
it to the bottom of Bugzilla. That way, testers can just Ctrl +
F for test plan, find the lowest one, and just consider that in
their testing.
<br>
<br>
What do you all think?
<br>
<br>
David Cook
<br>
<br>
Systems Librarian
<br>
<br>
Prosentient Systems
<br>
<br>
72/330 Wattle St
<br>
<br>
Ultimo, NSW 2007
<br>
<br>
Australia
<br>
<br>
Office: 02 9212 0899
<br>
<br>
Direct: 02 8005 0595
<br>
<br>
<br>
<br>
_______________________________________________
<br>
Koha-devel mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
<br>
website : <a class="moz-txt-link-freetext" href="http://www.koha-community.org/">http://www.koha-community.org/</a>
<br>
git : <a class="moz-txt-link-freetext" href="http://git.koha-community.org/">http://git.koha-community.org/</a>
<br>
bugs : <a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a>
<br>
</blockquote>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Koha-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="moz-txt-link-freetext" href="http://www.koha-community.org/">http://www.koha-community.org/</a>
git : <a class="moz-txt-link-freetext" href="http://git.koha-community.org/">http://git.koha-community.org/</a>
bugs : <a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--
Liz Rea
Catalyst.Net Limited
Level 6, Catalyst House,
150 Willis Street, Wellington.
P.O Box 11053, Manners Street,
Wellington 6142
GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7</pre>
</body>
</html>