I just went through the process of installing testlink for internal test case management, so I thought my experiences were worth a blog post.
Testlink 1.7 is an online testcase management system. It allows you to manage the testing cycle by managing test plans, test cases, test execution results.
Test link is integrated with a php database and is easily installed on a lamp stack.
Great instructions and information on installing and managing testlink can be found in the following links or at the test link website. The details in these documents goes far beyond the details in this doc. I’ll just outline some of the specific settings I used when configuring testlink
Test link website: http://www.teamst.org/
1. Install background services
* You need to make sure that the required services are installed on the machine. Mainly apache, mysql, php. Additionally, you need to install the php_mysql adapter. I needed to install this. In order to do so I actually re-compiled the php code this time including the mysql adapter. I recently found out that I could have just installed the mysql_php adapter using yum unlike what I had originally thought.
2. Tranfer the testlink installation zip and uncompress files into /home/repos/testlink
* The testlink zip file can be found on their website or at:
3. Point apache at the install directory by adding /etc/httpd/conf.d/testlinnk.conf with the following contents:
3. Change the owner of /home/repos/testlink to apache apache
– chmod apache.apache /home/repos/testlink
4. I never could actually get the security configurations correct with SELinux so that apache would actually serve the page. So I ….. disabled SELinux
– $ Echo 0>/selinux/enforce
To re-enable you’d add the following:
– $ Echo 1>/selinux/enforce
I also believe that when the machine is rebooted, seLinux may be re-enabled so testlink might just stop working.
5. Generate database tables and add data (create default or transfer from previous db)
– Go to http://localhost/testlink and login with admin admin (default which should be changed.)
– Follow the installation defeaults.
– All should go swimmingly and you’ve got a testlink instance up and running
– At this point you should be ready to add test plans, projects, test runs, users yada yada yada
- Note – as good as I think testlink is, it’s a bit week in it’s integration with bug tracking system. It essentially allows you to launch jira within testlink to create a bug, and then manually add the bug id to a test result.
- Test results show the bugs attached to them and these bugs can be launched from within testlink (which is kinda nice). Also, when a bug is resolved, it shows up as struck out within the test execution record.
- Edit /home/repos/testlink/testlink_170/custom_config.inc.php file to specify that it is integrating with JIRA for bug tracking.
- Edit /home/repos/testlink/testlink_170/cfg/jira.cfg.php to point at the jira instance (database, database user, etc).
Restart httpd and you’re good to go.