Enhance requirements funcionality
Moderators: Amaradana, TurboPT, TL Developers
Enhance requirements funcionality
Hi all,
first of all congratulations to all the developers and managers, I think Testlink is a great tool, it can hardly be given more for less.
Compared to the great functionality available for testing I think that requirements support is a little bit poor nowadays and I wish to suggest a couple of enhancements:
- Allow references to other requirements
- Enable additional fields/custom fields
- Enable requirement and document versions
Is any of those enhancements planned for next releases?
Many thanks.
first of all congratulations to all the developers and managers, I think Testlink is a great tool, it can hardly be given more for less.
Compared to the great functionality available for testing I think that requirements support is a little bit poor nowadays and I wish to suggest a couple of enhancements:
- Allow references to other requirements
- Enable additional fields/custom fields
- Enable requirement and document versions
Is any of those enhancements planned for next releases?
Many thanks.
Hi fman,
I've got no doubts about the main goal for Testlink development but I consider that there is a gap between test and requirement management tools that only Testlink can fill.
That gap arises because Testlink allows a link between a requirement and a test case. It is great that it allows TC versions but, what happens with requirements versions? In systems with early requirement specs the TC become obsolete quite frequently and it'd be great to track what TCs should be updated after changes in the requirements.
Then if it's considered that enhancement, it may be worth to add a little more functionality to the requirements management, not to create a full manager but at least for enabling a big new functionality for a not so big effort.
By the way, can you recommend any open source reqs manager?
Many thanks for your reply.
Antonio.
I've got no doubts about the main goal for Testlink development but I consider that there is a gap between test and requirement management tools that only Testlink can fill.
That gap arises because Testlink allows a link between a requirement and a test case. It is great that it allows TC versions but, what happens with requirements versions? In systems with early requirement specs the TC become obsolete quite frequently and it'd be great to track what TCs should be updated after changes in the requirements.
Then if it's considered that enhancement, it may be worth to add a little more functionality to the requirements management, not to create a full manager but at least for enabling a big new functionality for a not so big effort.
By the way, can you recommend any open source reqs manager?
Many thanks for your reply.
Antonio.
tstr,
One feature that has been added in 1.8 is a requirements tree. Details in this thread.
http://www.teamst.org/phpBB2/viewtopic.php?t=1333
MArk B.
One feature that has been added in 1.8 is a requirements tree. Details in this thread.
http://www.teamst.org/phpBB2/viewtopic.php?t=1333
MArk B.
I agree to that. Requirements Management can become quite sophisticated. We use separate requirements management and I need to export changes into testlink.fman wrote:main TL focus is test management, not requirement management, for req management our idea is use another specific open source tool.
Now that does mean that I need two features:
a) versions of requirements (so that I can do impact analysis)
b) the ability to extract the link between requirements and test cases via the API
a) is essential to me. b) is a very nice to have. It means I can manage all my traceability in my requirements management tool.
Cheers
Stephan
Hey fman,fman wrote:main TL focus is test management, not requirement management, for req management our idea is use another specific open source tool.
I spent a couple of hours yesterday on source forge trying to find a decent req management tool and came up short. There are a several there of course but none of them seems to be full featured AND active. Which one(s) were you guys thinking of integrating with?
MArk B.