TestLink

It's apparently a rudimentary and convenient Testcase reuse convention. For example, including the ghost string of another Testcase in the description of a new Testcase makes a link to that other Testcase. If it's more than that I hope someone else will respond to this thread.

Is TestLink, specifically version 1.9.6, safe to use with MySQL's, transaction compliant, row-locking, InnoDB storage engine?

Using 1.9.3 we're suddenly unable to successfully create new Test Projects with consistent DB records. The nodes_hierarchy table gets a new entry with a new id, for example 102020. The mysql_insert_id, however is, for example 8545055, and that becomes the id value for the testprojects table. The new...

Is anyone having trouble making a new state report in a "best case" manner, like it does for 'blocked'? My "how to make new exec status best case in chart" posting has more details http://www.teamst.org/forum/viewtopic.php?f=11&t=6689

I made a new execution status of in_prog. I made all the changes listed in other postings and everything including colors is working beautifully. However, the chart report is showing my new in_prog status in a worst case manner. In other words, if a given test case was in_prog for earlier builds, bu...

I copied a working config_db.inc.hp from a 1.9beta5 installation, but that is giving the following. Fatal error: require_once() [function.require]: Failed opening required 'ADODB_db_type.class.php' (include_path='.;C:\php5\pear;.;C:\wamp\www\testlink_cvs\lib\functions\;C:\wamp\www\testlink_cvs\third...

I checked out the latest code from cvs to play with beta6. The config_db.in.php file appears to be missing and causes the following error during installation.

Writing configuration file: Failed!

TestLink couldn't write the config file. Please copy the following into the ../config_db.inc.php file:

I understand it's not recommended to use any beta version for live testing. However, I'm still considering because of compelling reasons to want the Platform feature in particular. So, I'm wondering how close is 1.9beat5 to being production quality and what known risks might be. I'm performing my ow...

We're using a customized version of 1.8.5 and considering migrating to 1.9beta5 to make use of features like Platforms and Test Steps and other report improvements. Local customizations we put in place are + 'In Progress' result status throughout all functions including reports + Undo previous, indi...