Hi David,
for me it's just the other way around. As test plans often need to be
updated while a bug moves through the process I like taking a look at
the commit messages to find the latest instructions. It also means that
the plans end up in git, which can be quite helpful.
Katrin
On 04.10.2017 01:56, David Cook wrote:
Hi all,
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.
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.
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.
What do you all think?
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
_______________________________________________
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/
_______________________________________________
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/
