Re: [Libreoffice-qa] [​A​N​N​]​ ​M​o​z​t​r​a​p​ ​e​v​a​l​u​a​t​i​o​n​ ​o​n​l​i​n​e​ - roles and permissions

2012-05-23 Thread Petr Mladek
Yifan Jiang píše v St 23. 05. 2012 v 10:53 +0800:
> At the moment, the test suites are divided into different priorities (P1, P2,
> P3, P4), accordingly we can create test runs based on the priority:
> 
> - For Full Regression Test of a major version is to include all priority
> of cases to a test run.
> 
> - For Regression Test of a bug fix minor version is to include high (P1
> and P2) priority of cases to a test run.
> 
> Those were what we did in Litmus era.

The proposal of what test scenario belongs to what priority is described
at
http://wiki.documentfoundation.org/QA/Testing/Test_Cases_Organization#Priority


Just to explain some more background :-)

Litmus allows to split test cases in two levels: "test group" and
"subgroup". We used "test groups" to split by component, e.g. Writer,
Calc. We used subgroup to split by priority, e.g. P1, P2.

Moztrap has only one level called "Test Suites". It allows to run only
the whole "test suite". We might want to run only "P1" and maybe "P2"
tests for bugfix releases => Yifan had the great idea to split test
suites by priorities.

Note that Moztrap allows to add any tag for each test case. We could use
the tags for marking component-specific bugs. It is easy. Test cases
authors just select from list of available tags that is provided by
administrator.


Best Regards,
Petr

___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] [​A​N​N​]​ ​M​o​z​t​r​a​p​ ​e​v​a​l​u​a​t​i​o​n​ ​o​n​l​i​n​e​ - roles and permissions

2012-05-22 Thread Yifan Jiang
Hi Nino,

On Tue, May 22, 2012 at 07:38:21PM +0200, Nino wrote:
> Hi again,
> 
> Could you please grant me a test creator role, I want to try out
> entering test cases.

Of course, done! If no special reasons, please add the cases to "Version 0",
it will automatically apply to later versions of the case if "And Later
Versions" checkbox is checked on. The creator only allows an increased
operation of the test base, but do not worry about messing up things when you
try to play them :)

> BTW: Do we have a higher level test plan or test strategy? Which
> e.g. states what has to be tested for which purpose / in which
> situation? I'm wondering if/how some kind of mapping could be
> achieved between a requirement/use case/spec, a (or several) program
> function(s), and a set of corresponding test cases.

Great question! It is about how we organize the testing. The full strategy and
planning is evolving and I don't think we have a definite tone here :) Though
we have some tenative thoughts.

The current plan, from Litmus experience, is to have a stable test case base,
which we put into different "test suites". Test suites are allowed to include
to a "test run". And the test run is what a tester usually see from the Run
Tests view.

At the moment, the test suites are divided into different priorities (P1, P2,
P3, P4), accordingly we can create test runs based on the priority:

- For Full Regression Test of a major version is to include all priority
of cases to a test run.

- For Regression Test of a bug fix minor version is to include high (P1
and P2) priority of cases to a test run.

Those were what we did in Litmus era. The good thing of Moztrap is the test
suite and case management is more clear and flexible, we can always create
special test suites on demand, including a particular set of test cases. Then
we can create a particular test run from those test suites.

BTW, you will need to setup a local moztrap instance, or to be a "Manager"
permission to play with all of these management stuff :)

-- 
  Yifan Jiang
  Libreoffice / SuSE
  Contact: yifan - irc.freenode.net/libreoffice
  =  
  http://www.libreoffice.org/
  http://www.documentfoundation.org/
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: [Libreoffice-qa] [​A​N​N​]​ ​M​o​z​t​r​a​p​ ​e​v​a​l​u​a​t​i​o​n​ ​o​n​l​i​n​e​ - roles and permissions

2012-05-22 Thread Nino

Hi again,

Could you please grant me a test creator role, I want to try out 
entering test cases.


BTW: Do we have a higher level test plan or test strategy? Which e.g. 
states what has to be tested for which purpose / in which situation? I'm 
wondering if/how some kind of mapping could be achieved between a 
requirement/use case/spec, a (or several) program function(s), and a set 
of corresponding test cases.


Nino
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


[Libreoffice-qa] [​A​N​N​]​ ​M​o​z​t​r​a​p​ ​e​v​a​l​u​a​t​i​o​n​ ​o​n​l​i​n​e​ - roles and permissions

2012-05-22 Thread Yi Fan Jiang
Dear fellows,

This mail is part of the main thread of Moztrap evaluation online.

By default, Moztrap allows Guest touring of the system. Without any
registration, anyone can review testing result and how they organized. For
practical evaluation of the system, you should have either of the following
roles.

Tester role
===

Natively Moztrap supports either Mozilla Persona ID or traditional
registered way of log in. Since using and hacking to support those method
or OpenID solution is still pending, we only enabled the traditional way
at the moment. After a successful registration, you will be automatically
assigned as a tester, namely you could run test cases when the id is
born :)

Test creator role
=

If you have test cases on hand and want to contribute the test case base,
please do not hesitate to let me know :)

In addition, as the format of test case, I feel it would be convenient to
follow the Moztrap "Bulk test case" entry rule, that a text based test case
can be stored and exchanged conveniently. More details of how it works can 
be
found:


http://readthedocs.org/docs/moztrap/en/1.0.X/userguide/ui/import.html#bulk-test-case-entry-formats

Admin role
==

Admins could organize test runs, test cases organizations etc.

Litmus admins, please let me know when registered, I'll assign
corresponding admin permission for you.

If some one out of Litmus admin team who wants to try the test case
management tasks, please show off your previously proven contribution to
Libreoffice project. Admins would evaluate and decide the granting of
permission.

Best wishes,
Yifan


___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/