Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=SCS_TEST_TRACKING_SETUP_R2, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

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.
• Check if all team members have an account with appropriate permissions.

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

• Thoroughly research testlink's user documentation
• You can download .pdf document from ​http://www.teamst.org/index.php?option=com_content&task=view&id=11&Itemid=32
• In the document there are instructions and examples of how to set up SMTP server.
• The documentation of testlink 1.7 is more detailed and suitable for us than the documentation of testlink 1.8, because we are using testlink 1.7.4.
• Install SMTP server - postfix
• Integrate SMTP server and testlink editing sophie:/home/scs/testlink/custom_config.inc.php, i.e:

  $g_tl_admin_email = 'pacitu@gmail.com';
  $g_from_email = 'testlink@sophie2.org';
  $g_return_path_email = 'no_replay@sophie2.org';
  $g_mail_priority = 5;
  $g_smtp_host = 'localhost';
  

• You need admin account for testlink for the next steps
• From User administration -> View roles revise and decide different privileges about different types of users.

Implementation

• After research of testlink user documentation some attempts were made, until we have the best result
• Now testlink sends mail with new password to the mail that was assigned to each testlink user
• Integration between testlink and smtp server was made as described in design (by editing sophie:/home/scs/testlink/custom_config.inc.php):

  $g_tl_admin_email = 'pacitu@gmail.com';
  $g_from_email = 'testlink@sophie2.org';
  $g_return_path_email = 'no_replay@sophie2.org';
  $g_mail_priority = 5;
  $g_smtp_host = 'localhost';
  

• Roles and privileges were redefined, in future we probably will remove some obsolete user types.

Testing

Comments

^{(Write comments for this or later revisions here.)}