TestLink

Our automation reports the test results in a specific test plan.

Each automation run creates a new build within the test plan.

The automation updates the test case(s) result( referencing the test case name in the test plan which are well known names between Testlink and the automation application.)

We have been using the XMLRPC interface to update automated results in TL. We use the Perl XMLRPC::Lite module to accomplish this.

Yes, you're right. You do need to change the colour in the style sheet and add the displayable text in the strings file. I've added a new status that works for reports, charts, etc and did not need to modify any other code but the custom config. Here is what I added for a new status called ready_to_...

Adding a new result status is very easy and can be localized to your custom config file. There was no need for code changes.

I found that after defining the new status in my custom_config, I needed to added the addition statements. For a complete detail, here is what I defined for a status of ready_to_run $tlCfg->results['status_code'] = array ( "failed" => 'f', "blocked" => 'b', "passed" => ...

With RC5, there is no block of colour to the left of the testcase, the complete test case name is coloured.

I'd add a screen shot to the discussion but I can't figure out how

Here are the options I used: //Set the bug tracking system Interface to JIRA 3.1.1 /** The DB host to use when connecting to the JIRA db */ define('BUG_TRACK_DB_HOST', 'hostname'); /** The name of the database that contains the jira tables */ define('BUG_TRACK_DB_NAME', 'jiradb_3_13_2'); /** The DB ...

I guess I wasn't clear on my thoughts. I was interested if other users agreed with my view and if so, could the default colours be changed.

I do not like the pastel colours used in the execute tree. I would prefer that the colours be the same as in the Test Result dialog.

Basically, if the failed result is red then it should be red in the tree not pink.

Jira 3.13.2 ( mysql) and 1.8 RC5 is working for me

When I run the same mysql as in testcase.class.php for get_by_name, I am returned 8135 entries from the query Here is the sample of the sql, I used mysql> select distinct NHA.id,NHA.name,NHB.parent_id,TCV.tc_external_id from nodes_hierarchy NHA, nodes_hierarchy NHB, tcversions TCV where NHA.name = '...

These options are defined in the config.inc.php file. To change them, you should follow best practices and make the changes in custom_config.inc.php.

Using 1.8rc4 api

When I look at the response to a getTestCaseIdByName, I see 8000 plus instances of the testcase, all with a different external id. This doesn't make seen to me. Why would there be so many external ids associated with a test case I just created yesterday

There are 2 options you can configure depending on what you want to do. // ENABLED -> user can edit executed tc versions // DISABLED -> editing of executed tc versions is blocked. [STANDARD BEHAVIOUR] $tlCfg->testcase_cfg->can_edit_executed = ENABLED; // 1 -> user can edit execution notes, on old ex...

After adding a new result status via the custom_config.inc.php file, I found that I needed to modify themes/default/css/testlink.css to handle the colours in the execute tree and history of the test case execution ( colour code the status). I would prefer to handle this css change some where else (l...