Template for the verification process in redmine (QA)

howto

#1

If others testing team members are interested, i’m using this template for the verification process in redmine, i think it’s self-explanatory:

GENERAL WORKFLOW

    1. status of test box and list of packages/groups  currently installed
    2. replicate problem in detail
    3. install new package
    4. repeat testing above (2nd line)
    5. fixed/not fixed based on new testing, conclusion: VERIFIED or TRIAGED
    6. Misc Notes (Documentation Impact, other..)

VERIFICATION TEMPLATE

+System and  Package Version installed+
...
Package Installed: ...
Other Package installed: ...

+Test Original Problem+
...

+Install Updated Package+
<pre>
yum --enablerepo=nethserver-testing update ... 
</pre>

+Test Results after update+
...

+Verified Or Reopen+
...

+Note+
...

AS AN EXAMPLE:

+System and  Package Version installed+
[description of test system (version, installation methods, upgrade history. etc).
Package Installed: [rpm -qa <package name>]
Other Package installed: [yum grouplist | sed  '1,/Installed/d;/Available/,$d']

+Test Original Problem+
[Reproduce bug if you can, showing steps taken]

+Install Updated Package+
[Update to new package, show steps taken]
<pre>
yum --enablerepo=nethserver-testing update ... 
</pre>

+Test Results after update+
[Repeat steps carried out under TESTING above.]

+Verified Or Reopen+
[Problem fixed, then VERIFIED - not fixed, then TRIAGE]

+Note+
[Documentation Impact]
[Other]

note: maybe to comply the point 2 of the workflow, it would be nice that when a new bug is opened it contains

  1. status of test box and list of packages/groups currently installed
  2. howto replicate problem in detail

IMVHO :sweat_smile:

EDIT: just updated by @alefattorini with last @dz00te updates


Wrong column in Pop3 Connector view table
[SOLVED] NethServer 6.7 Beta1 - DHCP server module
New nethserver-adagios package needs QA
Building Quality Team
Building Quality Team
Building Quality Team
(Alessio Fattorini) #2

Yes! It might be so helpful! @vcc, @mabeleira, @medworthy, @fasttech


Community Digest 3 - June 2015
(Alessio Fattorini) #3

@vcc @nrauso @davidep @giacomo what do you think? Any advice? Could we extend it with some tips about QA? I really want Guidelines for a good QA process


(Giacomo Sanchietti) #4

I like it!


(Alessio Fattorini) #5

We can start from this good page:
http://wiki.contribs.org/SME_Server:Documentation:QA:Verification


#6

yes, really good point. I like it it’s better and more detailed of what i’m using now.
a little update based on sme_qa and on the template i’m currently using:

GENERAL WORKFLOW

    1. status of test box and list of packages/groups  currently installed
    2. replicate problem in detail
    3. install new package
    4. repeat testing above (2nd line)
    5. fixed/not fixed based on new testing, conclusion: VERIFIED or TRIAGED
    6. Misc Notes (Documentation Impact, other..)

VERIFICATION TEMPLATE

+System and  Package Version installed+
...
Package Installed: ...
Other Package installed: ...

+Test Original Problem+
...

+Install Updated Package+
<pre>
yum --enablerepo=nethserver-testing update ... 
</pre>

+Test Results after update+
...

+Verified Or Reopen+
...

+Note+
...

AS AN EXAMPLE:

+System and  Package Version installed+
[description of test system (version, installation methods, upgrade history. etc).
Package Installed: [rpm -qa <package name>]
Other Package installed: [yum grouplist | sed  '1,/Installed/d;/Available/,$d']

+Test Original Problem+
[Reproduce bug if you can, showing steps taken]

+Install Updated Package+
[Update to new package, show steps taken]
<pre>
yum --enablerepo=nethserver-testing update ... 
</pre>

+Test Results after update+
[Repeat steps carried out under TESTING above.]

+Verified Or Reopen+
[Problem fixed, then VERIFIED - not fixed, then TRIAGE]

+Note+
[Documentation Impact]
[Other]

note: maybe to comply the point 2 of the workflow, it would be nice that when a new bug is opened it contains

  1. status of test box and list of packages/groups currently installed
  2. howto replicate problem in detail

IMVHO :sweat_smile:


(Alessio Fattorini) #7

Good, like it. What do you think @vcc ?


(Vasco) #8

Good,

It as all the information needed


(Giacomo Sanchietti) #9

I like it!

alefattorini
Alessio Fattorini
Community Manager

    July 10

@vcc @nrauso @davidep @giacomo what do you think? Any advice? Could we extend it with some tips about QA? I really want Guidelines for a good QA process

To respond, reply to this email or visit http://community.nethserver.org/t/template-for-the-verification-process-in-redmine/1067/3 in your browser.


Previous Replies

alefattorini
Alessio Fattorini
Community Manager

    June 17

Yes! It might be so helpful! @vcc, @mabeleira, @medworthy, @fasttech

dz00te
Testing Team Member

    June 17

if others testing team members are interested, i’m using this template for the verification process in redmine, i think it’s self-explanatory:

> 
> +System and Package Version installed+ ... Package Installed: xxxx Other Package installed: xxxx +Test Original Problem+ ... +Install Updated Package+ <pre> yum --enablerepo=nethserver-testing update ... </pre> +Test Results after update+ ... +Note+ ...