Difference between revisions of "TCM wishes"
From Apache OpenOffice Wiki
(→General Enhancements) |
(→available infos) |
||
| (15 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Quality Assurance]] | [[Category:Quality Assurance]] | ||
| − | TCM is used for localization testing and result tracking. But for better acceptance TCM ( the tool and the process) could be enhanced. This page could be used to collect wishes. | + | TCM (Test Case Management) is used for localization testing and result tracking. But for better acceptance TCM (the tool and the process) could be enhanced. This page could be used to collect wishes. |
| − | = | + | = Available infos= |
* [http://l10n.openoffice.org/localization/About_TCM.html about TCM] | * [http://l10n.openoffice.org/localization/About_TCM.html about TCM] | ||
| − | * [http://www.sunvirtuallab.com/tcm2/tcm_login.cgi TCM login] | + | * [http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo TCM login] |
= General Enhancements = | = General Enhancements = | ||
* TCM should be open source (L)GPL - so community could be more active in improving TCM. | * TCM should be open source (L)GPL - so community could be more active in improving TCM. | ||
| − | * Decide if TCM designs the '''management software''' or the bundle of it with the '''testcases'''. | + | * Decide if the name TCM designs the '''management software''' or the bundle of it with the '''testcases'''. |
* The free license should apply to ''both'' components; LGPL could be a problem since it would [http://www.openoffice.org/FAQs/faq-licensing.html#11 ''probably'' allow linking] the management software to proprietary testcases; the problems the community has now in accessing and modifying testcases risk not being solved unless the whole (TCM+testcases) is '''GPL'''ed. But testcases are not source code, so the definition of ''linking'' must be interpreted somehow. | * The free license should apply to ''both'' components; LGPL could be a problem since it would [http://www.openoffice.org/FAQs/faq-licensing.html#11 ''probably'' allow linking] the management software to proprietary testcases; the problems the community has now in accessing and modifying testcases risk not being solved unless the whole (TCM+testcases) is '''GPL'''ed. But testcases are not source code, so the definition of ''linking'' must be interpreted somehow. | ||
| Line 24: | Line 24: | ||
* option to hide outdated test cycles in test assignment and test result update | * option to hide outdated test cycles in test assignment and test result update | ||
* implementation of test types (e.g. release test, feature test) | * implementation of test types (e.g. release test, feature test) | ||
| + | * It should be possible to localize the interface. | ||
| + | * There should be some more explanations. | ||
| + | * anonymous access to Test Cases as well as Summary / Detail Report | ||
| + | * Ability to log in with the AOo login | ||
== test case maintenance == | == 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 | ||
| + | * it should be easy to add new tests samples and to update them when needed | ||
| + | * 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 | ||
== test reports == | == test reports == | ||
| + | |||
| + | * Summary of passed / failed / skipped test cases per category (would help to identify untested or only partial tested categories) | ||
== test assignments == | == test assignments == | ||
| − | * | + | * It should be possible to assign testcases to more than one tester. |
| + | * 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. | ||
== test result updates == | == test result updates == | ||
| + | |||
| + | * First-time testers need guidance with this; a ''My tests'' menu option would be better. | ||
Latest revision as of 15:46, 28 August 2022
TCM (Test Case Management) is used for localization testing and result tracking. But for better acceptance TCM (the tool and the process) could be enhanced. This page could be used to collect wishes.
Contents
Available infos
General Enhancements
- TCM should be open source (L)GPL - so community could be more active in improving TCM.
- Decide if the name TCM designs the management software or the bundle of it with the testcases.
- The free license should apply to both components; LGPL could be a problem since it would probably allow linking the management software to proprietary testcases; the problems the community has now in accessing and modifying testcases risk not being solved unless the whole (TCM+testcases) is GPLed. But testcases are not source code, so the definition of linking must be interpreted somehow.
Process Enhancements
- community should have the ability to define new builds for testing
Tool Enhancements
general
- option to hide outdated test cycles in test assignment and test result update
- implementation of test types (e.g. release test, feature test)
- It should be possible to localize the interface.
- There should be some more explanations.
- anonymous access to Test Cases as well as Summary / Detail Report
- Ability to log in with the AOo login
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
- it should be easy to add new tests samples and to update them when needed
- 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
test reports
- Summary of passed / failed / skipped test cases per category (would help to identify untested or only partial tested categories)
test assignments
- It should be possible to assign testcases to more than one tester.
- 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.
test result updates
- First-time testers need guidance with this; a My tests menu option would be better.
