Hi,
My company is currently looking for a test management software, and TestLink is at this time the best candidate we have.
However, is does not completely fit out needs,
and we are thinking about implementing the missing
features.
In this scheme, our concern is whether or not our contribution would be of interest for the TestLink mainline.
Here is a short list of what we are thinking about (please tell me if some of them already belong to scheduled evolutions, or if there are already existing features that I might have not seen):
- have a 2D matrix of links between requirements and tests
- have a step-by-step result for test runs
- have a way to archive several run results of a test case
- have a callback for automated tests in order to launch them, and a log parser of a formatted output
and, optionally:
- have an automated dated test run report
- have permissions rights on custom fields
- have a "tester help tip" column in the test cases
- have an approval mechanism for created or modified requirements, test cases, and test reports
Best regards
Thierry
Suggested enhancements and new features to Testlink
Moderators: Amaradana, TurboPT, TL Developers
Re: Suggested enhancements and new features to Testlink
We collect any kind of request ONLY Through mantis, with one ticket for each request.
Please follow this approach.
We are interested on any kind of feature contribution. Again this is not the channel to talk with dev team.
You can send me an email (francisco.mancardi@gmail.com).
In anycase we accept features analize them and then make our choice of add to stable code => we will take charge of mantainance
do not accept as official code => we do not accept issue reports, questions and so on.
In order to have a good relationship we request that code that can be consider candidate for inclusion on stable code follow absolutely our
development standards (as is done for each open source app where you want to collaborate).
In addition you have to understood that when we analize the proposed feature we have to give more wider look that the contributor, because we need to understand impacts ON WHOLE system.
This is the case of feature ' Add results to steps', that have LOTS of side effects (already discussed on all issues reported of this subject on Mantis).
We tend to avoid after features that can have negative impacts on performance .
we have worked a lot on 1.9.4 to fix performance issues that WERE PRODUCED BY DEVELOPMENT TEAM.
Best regards
Francisco Mancardi
TestLink Team Leader
Please follow this approach.
We are interested on any kind of feature contribution. Again this is not the channel to talk with dev team.
You can send me an email (francisco.mancardi@gmail.com).
In anycase we accept features analize them and then make our choice of add to stable code => we will take charge of mantainance
do not accept as official code => we do not accept issue reports, questions and so on.
In order to have a good relationship we request that code that can be consider candidate for inclusion on stable code follow absolutely our
development standards (as is done for each open source app where you want to collaborate).
In addition you have to understood that when we analize the proposed feature we have to give more wider look that the contributor, because we need to understand impacts ON WHOLE system.
This is the case of feature ' Add results to steps', that have LOTS of side effects (already discussed on all issues reported of this subject on Mantis).
We tend to avoid after features that can have negative impacts on performance .
we have worked a lot on 1.9.4 to fix performance issues that WERE PRODUCED BY DEVELOPMENT TEAM.
Best regards
Francisco Mancardi
TestLink Team Leader