Requirement Specification- Add chapters for descriptions

[hjw]

Hi,

i would like to write a "complete" requirement specification in test link.
The current problem with testlink is that it just has one scope chapter and that then every subchapter has to be a requirement.

However if you write full requirement specifications, you often have text that describes the topic and explains scenarios based on pictures, tables These chapters are not necessarily requirements and you don't want to count these.

Is it possible to use the same concepts that you have for Test cases (i.e. TestSuites, that contain test suites that may contain test cases) for
Requirements?

I.e. you have a RequirementSuite, that can contain RequirementSuites, which can or may not contain requirements.

This way you can generate a document that can resembles a real specification.

Any comments?

[havlatm]

Configure:

Code: Select all

$tlCfg->req_cfg->child_requirements_mgmt = ENABLED;

Warning: not all functionality works in this mode properly as this is a new feature in 1.8. For example Import/Export doesn't support n-level structure, yet.

[hjw]

Thanks, the substructure now shows off.

Is there an easy way to add the same printing capability as you have
with the "Generate Test Specification Document", i.e. offer html/word/openOffice export capability?

Print only works on a per "Specification" level, but not for the whole document.

How can i add a "Generate Requirement Specification Document" button and use the same functionality as the "Generate Test Specificaion Document". Which source file contains this - i may try to add this.