Version 5 (modified by deyan, 16 years ago) (diff) |
---|
Analysis
Overview
In this revision the current setup of TestLink should be improved
Task requirements
Requirements from the previous revision
- SMTP server should be set up - The smtp server is needed in order to send forgotten passwords.
- Permissions should be cleared -
- Registered users should have the permission to view the tests and add comments if possible.
- Team members should have the permission to view, edit and execute tests (create test plans, etc).
Requirements for this revision
- Integration between trac and testlink is needed. The documentation for this is in related section.
Task result
TestLink with trac integration. Appropriate permissions and ability to create an account.
Implementation idea
A fragment from the user documentation of testlink:
Copy the following lines from config.inc.php to custom_config.inc.php. // ---------------------------------------------------------------------------- /** [Bug Tracking systems] */ /** * TestLink uses bugtracking systems to check if displayed bugs resolved, verified, * and closed bugs. If they are it will strike through them * * NO : no bug tracking system integration * BUGZILLA : edit configuration in TL_ABS_PATH/cfg/bugzilla.cfg.php * MANTIS : edit configuration in TL_ABS_PATH/cfg/mantis.cfg.php * JIRA : edit configuration in TL_ABS_PATH/cfg/jira.cfg.php * TRACKPLUS : edit configuration in TL_ABS_PATH/cfg/trackplus.cfg.php */ $g_interface_bugs='NO'; On custom_config.inc.php change line: $g_interface_bugs='NO'; Final result: $g_interface_bugs='MANTIS'; tl-
This configuration is for mantis. Trac config should be similar. In testing section you may create a new user account to test the setup.
Related
http://www.teamst.org/_tldoc/1.7/tl-bts-howto.pdf TestLink documentation page for integration with bugtracking system.
http://www.teamst.org/_tldoc/1.8/installation_manual.pdf TestLink 1.8 draft documentation.
How to demo
Show testlink and create a simple demonstation of testcase connected with a ticket.
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
(Write comments for this or later revisions here.)