Difference between revisions of "TCM Integration to QUASTe"

From Apache OpenOffice Wiki
Jump to: navigation, search
m
m
Line 1: Line 1:
−
<div style="width: 700px;">
+
= Scope =
 +
The development of the [http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo Test Case Management ('''TCM''')] site is stalled.
  
−
= '''2010-07-12''' =
+
Thus we plan to integrate the TCM to the Test Case Specification ('''TCS''') tool <br>which is hosted on the [http://quaste.services.openoffice.org/ Quality Assurance Status Page ('''QUASTe''')].
−
<div style="border: dotted 2px gray; padding: 5px;">
+
−
== Attendees: ==
+
−
RB, JA, HDE, ES
+
  
−
== Last Action Items: ==
+
On the current page you will find details about the team in charge of this integration,<br>the meeting minutes and the progress status of the whole project.
  
−
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0;  border: 1px #cccccc solid; border-collapse: collapse; width: 500px"
+
The "code name" of the project is: '''TCM@QUASTe''' (i.e. "TCM at QUASTe").
−
| width="300" bgcolor="#dddddd" | '''Owner/Description'''
+
−
| width="300" bgcolor="#dddddd" | '''Status'''
+
  
−
|-
+
= The Team =
−
| '''@HDE''': Evaluate the resources needed for QUASTe to support Unicode
+
−
| '''Done''': will be the first step to achieve. It should take less than 1 week to implement.
+
  
−
|}
+
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0;  border: 1px #cccccc solid; border-collapse: collapse; width: 500px"
 +
| width="300" bgcolor="#dddddd" |'''Name'''
 +
| width="300" bgcolor="#dddddd" |'''Role'''
 +
| width="300" bgcolor="#dddddd" |'''E-mail'''
  
−
== Discussion: ==
+
|-
−
'''HDE''': gave evaluation on Unicode support.
+
| Rafaella Braconi
 +
| Program Manager
 +
| rb@openoffice.org
  
−
'''ES''': took over to set up a Wiki page for the project including answers to some existing RFEs
 
−
 
−
== New Action Items: ==
 
−
 
−
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0;  border: 1px #cccccc solid; border-collapse: collapse; width: 500px"
 
−
| width="300" bgcolor="#dddddd" | '''Owner/Description'''
 
 
|-
 
|-
−
| '''@RB''': Announce the project when ES is done with setting up the Wiki page.
+
| Joost Andrae
 +
| Program Manager
 +
| ja@openoffice.org
  
 
|-
 
|-
−
| '''@HDE''': Implement Unicode support on QUASTe.
+
| Helge Delfs
 +
| QUASTe Development
 +
| hde@openoffice.org
  
 
|-
 
|-
−
| '''@ES''': set up a Wiki page for the project including answers to some existing RFEs
+
| Éric Savary
 +
| Quality Assurance
 +
| es@openoffice.org
  
 
|}
 
|}
−
== Next Meeting: ==
 
−
TBD
 
  
−
</div>
+
= Meeting Minutes =
  
 +
For the meeting minutes, click [[TCM_at_QUASTe_Meeting_Minutes | '''here''']]
  
−
<!-- 8< SCHNIPP-SCHNAPP  >8  -->
+
= Current Status =
 +
Investigating Unicode support of the TCS Tool
  
−
= '''Meeting Minute Template''' =
+
= Tool Enhancements RFEs =
−
<div style="border: dotted 2px gray; padding: 5px;">
+
The following sections present Requests For Enhancement (RFE) against the TCM as they have been published [http://wiki.services.openoffice.org/wiki/TCM_wishes here].
−
== Attendees: ==
+
−
RB, JA, HDE, ES
+
  
−
== Last Action Items: ==
+
== 4.1 General ==
−
 
+
* '''Option to hide outdated test cycles in test assignment and test result update'''<br>→ YES
−
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 500px"
+
* '''Implementation of test types (e.g. release test, feature test)'''<br>→ YES
−
| width="300" bgcolor="#dddddd" | '''Owner/Description'''
+
* '''It should be possible to localize the interface.'''<br>→ YES
−
| width="300" bgcolor="#dddddd" | '''Status'''
+
* '''There should be some more explanations.'''<br>→ Incomplete. Which explanations about what? Tutorial in progress
−
 
+
* '''Anonymous access to Test Cases as well as Summary / Detail Report'''<br>→ NO. There won’t be privileges and rights to write and change the tests anymore so that<br> the minimum is to know who makes what in order to make changes trackable and avoid low level sabotage.
−
|-
+
* '''Ability to log-in with the OOo log-in'''<br>→ YES
−
| '''@<team_member_shortname>''': <what was the last action item>
+
−
| '''<status>''' (''Done/In progress/Canceled''): <details about the status e.g. deadlines, evaluation...>
+
−
 
+
−
|}
+
−
 
+
−
== Discussion: ==
+
−
'''<attendee_shortname>''': <what has been said>.
+
−
 
+
−
== New Action Items: ==
+
−
 
+
−
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0;  border: 1px #cccccc solid; border-collapse: collapse; width: 500px"
+
−
| width="300" bgcolor="#dddddd" | '''Owner/Description
+
−
'''
+
−
|-
+
−
| '''@<team_member_shortname>''': | <details on the action item>
+
−
 
+
−
|}
+
−
== Next Meeting: ==
+
−
<YYYY-MM-DD or 'TBD'>
+
  
−
</div>
+
== 4.2 test case maintenance  ==
 +
* '''Community should be able to change English test descriptions.<br> If English description is changed, translated descriptions should be marked as "translation needs update".<br> This marker can be removed if translated test case is updated'''<br>→ YES
 +
* '''It should be easy to add new tests samples and to update them when needed'''<br>→ YES (As the TCS is already working now)
 +
* '''It would be nice to be able to maintain the test cases through our translation tools<br> and use Pootle as a repository so we are able to see when original test cases are changed'''<br>→ LATER
  
−
<!-- 8< SCHNIPP-SCHNAPP  >8  -->  
+
== 4.3 test reports  ==
 +
* '''Summary of passed / failed / skipped test cases per category <br>(would help to identify untested or only partial tested categories)'''<br>→ YES/LATER
  
 +
== 4.4 test assignments  ==
 +
* '''It should be possible to assign test cases to more than one tester.'''<br>->YES (like the CC field in IZ?)
 +
* '''Balance detail in the Operating Systems: we now have one ''Linux'' and five versions of ''Windows'';<br> we should have "Linux - RedHat/Fedora", "Linux - Debian/Ubuntu", "Linux - SUSE", "Linux - Mandriva", "Linux - Other";<br> then two read-only categories, ''Linux'' and ''Windows'', could be created to quickly see assignments.'''<br>→ NO. On the contrary, we will reduce the number on OS like in the automation results on QUASTe:<br> '''Linux, Mac, Solaris, Windows'''.<br> But one could think about a Comment field where the tester can freely mention the flavor of his OS.<br>Furthermore, one could imagine non mandatory and freely writable (no anarchic list boxes!) fields which can explain a difference in results:<br>- '''Architecture''': Ex: 32/64bits<br>- '''Window manager''': Ex: Gnome, KDE <br>Note: '''in a perfect world''' and in order to be able to compare (and find regressions) results from one release to an other,<br> '''testers "should"''' run the tests on the same OS (platform, environment)
  
−
</div>
+
== 4.5 test result updates  ==
 +
* '''First-time testers need guidance with this...'''<br>→ Duplicate of "&nbsp;There should be some more explanations&nbsp;" above
 +
* '''...a ''My tests'' menu option would be better.'''<br>→ YES: As in QUASTe.
  
 
[[Category:Quality Assurance]]
 
[[Category:Quality Assurance]]
Line 88: Line 75:
 
[[Category:Localization]]
 
[[Category:Localization]]
 
[[Category:Test Case Specification]]
 
[[Category:Test Case Specification]]
−
[[Category:Minutes]]
 

Revision as of 22:56, 19 July 2010

Scope

The development of the Test Case Management (TCM) site is stalled.

Thus we plan to integrate the TCM to the Test Case Specification (TCS) tool
which is hosted on the Quality Assurance Status Page (QUASTe).

On the current page you will find details about the team in charge of this integration,
the meeting minutes and the progress status of the whole project.

The "code name" of the project is: TCM@QUASTe (i.e. "TCM at QUASTe").

The Team

Name Role E-mail
Rafaella Braconi Program Manager rb@openoffice.org
Joost Andrae Program Manager ja@openoffice.org
Helge Delfs QUASTe Development hde@openoffice.org
Éric Savary Quality Assurance es@openoffice.org

Meeting Minutes

For the meeting minutes, click here

Current Status

Investigating Unicode support of the TCS Tool

Tool Enhancements RFEs

The following sections present Requests For Enhancement (RFE) against the TCM as they have been published here.

4.1 General

  • Option to hide outdated test cycles in test assignment and test result update
    → YES
  • Implementation of test types (e.g. release test, feature test)
    → YES
  • It should be possible to localize the interface.
    → YES
  • There should be some more explanations.
    → Incomplete. Which explanations about what? Tutorial in progress
  • Anonymous access to Test Cases as well as Summary / Detail Report
    → NO. There won’t be privileges and rights to write and change the tests anymore so that
    the minimum is to know who makes what in order to make changes trackable and avoid low level sabotage.
  • Ability to log-in with the OOo log-in
    → YES

4.2 test case maintenance

  • Community should be able to change English test descriptions.
    If English description is changed, translated descriptions should be marked as "translation needs update".
    This marker can be removed if translated test case is updated
    → YES
  • It should be easy to add new tests samples and to update them when needed
    → YES (As the TCS is already working now)
  • It would be nice to be able to maintain the test cases through our translation tools
    and use Pootle as a repository so we are able to see when original test cases are changed
    → LATER

4.3 test reports

  • Summary of passed / failed / skipped test cases per category
    (would help to identify untested or only partial tested categories)
    → YES/LATER

4.4 test assignments

  • It should be possible to assign test cases to more than one tester.
    ->YES (like the CC field in IZ?)
  • Balance detail in the Operating Systems: we now have one Linux and five versions of Windows;
    we should have "Linux - RedHat/Fedora", "Linux - Debian/Ubuntu", "Linux - SUSE", "Linux - Mandriva", "Linux - Other";
    then two read-only categories, Linux and Windows, could be created to quickly see assignments.
    → NO. On the contrary, we will reduce the number on OS like in the automation results on QUASTe:
    Linux, Mac, Solaris, Windows.
    But one could think about a Comment field where the tester can freely mention the flavor of his OS.
    Furthermore, one could imagine non mandatory and freely writable (no anarchic list boxes!) fields which can explain a difference in results:
    - Architecture: Ex: 32/64bits
    - Window manager: Ex: Gnome, KDE
    Note: in a perfect world and in order to be able to compare (and find regressions) results from one release to an other,
    testers "should" run the tests on the same OS (platform, environment)

4.5 test result updates

  • First-time testers need guidance with this...
    → Duplicate of " There should be some more explanations " above
  • ...a My tests menu option would be better.
    → YES: As in QUASTe.
Retrieved from "https://wiki.openoffice.org/w/index.php?title=TCM_Integration_to_QUASTe&oldid=176112"
Personal tools