(Created page with "== Introduction == The Fedora QA team is interested in exploring nitrate to replace our use of wiki for managing test results from community test events (e.g. test days, release...") |
|||
(5 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
The Fedora QA team is interested in exploring nitrate to replace our use of wiki for managing test results from community test events (e.g. test days, release validation etc...). This page introduced the current status of this nitrate project. | The Fedora QA team is interested in exploring nitrate to replace our use of wiki for managing test results from community test events (e.g. test days, release validation etc...). This page introduced the current status of this nitrate project. An introduction of Nitrate tcms system can be found at: wiki:http://fedorahosted.org/nitrate/. | ||
== Milestones == | == Milestones == | ||
There are 4 main milestones for | There are 4 main milestones for this migration project: | ||
# Use cases and features identification: we've been using wiki as our TCMS system, its use cases | # Use cases and features identification: we've been using wiki as our TCMS system, its use cases and the feature comparison between wiki and nitrate were identified in order to customize the required features against current Nitrate system. To improve and complete the feature lists, a pilot instance need be set up for community testing. Finally, the requirements should be raised to the tcms tools team for a customized nitrate system to fulfil our needs. | ||
# Pilot instance: Before formal and wide use, a pilot instance system is required for user experience and feedback. [https://fedorahosted.org/fedora-infrastructure/ticket/2673 Ticket#2673] has been filed tracking this issue as well as [http://lists.fedoraproject.org/pipermail/infrastructure/2011-August/010634.html the mail dialogs]. Note that though it's better to package nitrate first, setting up a dev version can be done in parallel with the review if the time is limited. | # Pilot instance: Before formal and wide use, a pilot instance system is required for user experience and feedback. [https://fedorahosted.org/fedora-infrastructure/ticket/2673 Ticket#2673] has been filed tracking this issue as well as [http://lists.fedoraproject.org/pipermail/infrastructure/2011-August/010634.html the mail dialogs]. Note that though it's better to package nitrate first, setting up a dev version can be done in parallel with the review if the time is limited. | ||
# Package Review: Nitrate should be packaged at least before the formal revision hosted into Fedora infra. The package has been actively under review at:https://bugzilla.redhat.com/show_bug.cgi?id=690728. | # Package Review: Nitrate should be packaged at least before the formal revision hosted into Fedora infra. The package has been actively under review at:https://bugzilla.redhat.com/show_bug.cgi?id=690728. | ||
# Formal nitrate version: When all the feature requirements have been gathered and package get reviewed, it's time to set up the final version. To propose a hosting space, file a ticket at: https://fedoraproject.org/wiki/Infrastructure/RFR along with a notification mail to infrastructure@lists.fedoraproject.org | # Formal nitrate version: When all the feature requirements have been gathered and package get reviewed, it's time to set up the final version. To propose a hosting space, file a ticket at: https://fedoraproject.org/wiki/Infrastructure/RFR along with a notification mail to infra mailing list (infrastructure@lists.fedoraproject.org). when the resources are available, file a ticket to tools team(tools-hosted-request@redhat.com) to require building a nitrate system. | ||
== | == TCMS Migration Project == | ||
A trac ticket has been filed at to track this event: https://fedorahosted.org/fedora-qa/ticket/152. | |||
=== Use cases and Feature Requirements === | === Use cases and Feature Requirements === | ||
* Wiki use cases have been summarized at: https://fedoraproject.org/wiki/Tcms_use_cases. | |||
* The feature comparison between wiki and nitrate are at: https://fedoraproject.org/wiki/Tcms_Comparison. | |||
* Finally, the required features are listed at: https://fedoraproject.org/wiki/Tcms_feature_requirements. | |||
Note that the requirement list need be further improved according to the feedback from a pilot instance to be set up for community testing. | |||
=== Package Review === | |||
= | Nitrate package is under review at: | ||
* https://bugzilla.redhat.com/show_bug.cgi?id=690728 | |||
Yuguang, the tools team member is actively working on the package as well as it bundled libraries. | |||
=== Nitrate Upstream Community === | === Nitrate Upstream Community === | ||
Nitrate has its own upstream community and the mail List is: nitrate-devel@lists.fedorahosted.org. It's encouraged to discuss the nitrate project there and keep the community active. | |||
nitrate-devel@lists.fedorahosted.org | |||
=== Auto scripts for Migration from wiki to nitrate === | === Auto scripts for Migration from wiki to nitrate === | ||
Git code: | Nitrate is able to import testopia format xml file, thus a script has been developed to transfer wiki test case page(s) to a xml file which can be imported to the nitrate system. Git code is available at: http://fedorapeople.org/gitweb?p=rhe/public_git/repo.git;a=tree. The detailed guidance of the script can be found at: https://fedoraproject.org/wiki/User:Rhe/Nitrate_Migration_Script. | ||
http://fedorapeople.org/gitweb?p=rhe/public_git/repo.git;a=tree | |||
=== Pilot Instance === | === Pilot Instance === | ||
=== TCMS | The ticket for hosting a space to Fedora infra is: | ||
* https://fedorahosted.org/fedora-infrastructure/ticket/2673 | |||
The dialog in the infra mail lists is: | |||
tools-hosted-request | * http://lists.fedoraproject.org/pipermail/infrastructure/2011-August/010634.html | ||
Note that one can even set up a dev instance first without the package getting reviewed as the reviewing is very time consuming, though it's better and more convenient to have the package before it. | |||
=== Formal Nitrate TCMS System === | |||
The basic steps include: | |||
# Make sure that the nitrate package is reviewed. | |||
# Gather all the feature requirements and raise them to tools team(tools-hosted-request@redhat.com). | |||
# File a ticket to infra asking for resources: https://fedoraproject.org/wiki/Infrastructure/RFR. Meanwhile, send a mail for notification to: infrastructure@lists.fedoraproject.org. | |||
# When the resources are available, ask the tools team to build the system by filing a ticket to: tools-hosted-request@redhat.com. | |||
# Maintain and update the system in the later time. | |||
=== Contacts === | |||
* Tools team contact: Yuguang Wang(yuwang), Danqing Li(dli), Victor Chen(vchen) | |||
* Nitrate package reviewer: Jens Peterson(juhp) | |||
Latest revision as of 10:35, 23 August 2011
Introduction
The Fedora QA team is interested in exploring nitrate to replace our use of wiki for managing test results from community test events (e.g. test days, release validation etc...). This page introduced the current status of this nitrate project. An introduction of Nitrate tcms system can be found at: wiki:http://fedorahosted.org/nitrate/.
Milestones
There are 4 main milestones for this migration project:
- Use cases and features identification: we've been using wiki as our TCMS system, its use cases and the feature comparison between wiki and nitrate were identified in order to customize the required features against current Nitrate system. To improve and complete the feature lists, a pilot instance need be set up for community testing. Finally, the requirements should be raised to the tcms tools team for a customized nitrate system to fulfil our needs.
- Pilot instance: Before formal and wide use, a pilot instance system is required for user experience and feedback. Ticket#2673 has been filed tracking this issue as well as the mail dialogs. Note that though it's better to package nitrate first, setting up a dev version can be done in parallel with the review if the time is limited.
- Package Review: Nitrate should be packaged at least before the formal revision hosted into Fedora infra. The package has been actively under review at:https://bugzilla.redhat.com/show_bug.cgi?id=690728.
- Formal nitrate version: When all the feature requirements have been gathered and package get reviewed, it's time to set up the final version. To propose a hosting space, file a ticket at: https://fedoraproject.org/wiki/Infrastructure/RFR along with a notification mail to infra mailing list (infrastructure@lists.fedoraproject.org). when the resources are available, file a ticket to tools team(tools-hosted-request@redhat.com) to require building a nitrate system.
TCMS Migration Project
A trac ticket has been filed at to track this event: https://fedorahosted.org/fedora-qa/ticket/152.
Use cases and Feature Requirements
- Wiki use cases have been summarized at: https://fedoraproject.org/wiki/Tcms_use_cases.
- The feature comparison between wiki and nitrate are at: https://fedoraproject.org/wiki/Tcms_Comparison.
- Finally, the required features are listed at: https://fedoraproject.org/wiki/Tcms_feature_requirements.
Note that the requirement list need be further improved according to the feedback from a pilot instance to be set up for community testing.
Package Review
Nitrate package is under review at:
Yuguang, the tools team member is actively working on the package as well as it bundled libraries.
Nitrate Upstream Community
Nitrate has its own upstream community and the mail List is: nitrate-devel@lists.fedorahosted.org. It's encouraged to discuss the nitrate project there and keep the community active.
Auto scripts for Migration from wiki to nitrate
Nitrate is able to import testopia format xml file, thus a script has been developed to transfer wiki test case page(s) to a xml file which can be imported to the nitrate system. Git code is available at: http://fedorapeople.org/gitweb?p=rhe/public_git/repo.git;a=tree. The detailed guidance of the script can be found at: https://fedoraproject.org/wiki/User:Rhe/Nitrate_Migration_Script.
Pilot Instance
The ticket for hosting a space to Fedora infra is:
The dialog in the infra mail lists is:
Note that one can even set up a dev instance first without the package getting reviewed as the reviewing is very time consuming, though it's better and more convenient to have the package before it.
Formal Nitrate TCMS System
The basic steps include:
- Make sure that the nitrate package is reviewed.
- Gather all the feature requirements and raise them to tools team(tools-hosted-request@redhat.com).
- File a ticket to infra asking for resources: https://fedoraproject.org/wiki/Infrastructure/RFR. Meanwhile, send a mail for notification to: infrastructure@lists.fedoraproject.org.
- When the resources are available, ask the tools team to build the system by filing a ticket to: tools-hosted-request@redhat.com.
- Maintain and update the system in the later time.
Contacts
- Tools team contact: Yuguang Wang(yuwang), Danqing Li(dli), Victor Chen(vchen)
- Nitrate package reviewer: Jens Peterson(juhp)