exec_status of getTestCasesForTestPlan() not equals last execution status

[chen2liang4]

two executions for one test case, exec_status is 'p' by calling getTestCasesForTestPlan() but status is 'f' by calling getLastExecutionResult()

getLastExecutionResult is correct, getTestCasesForTestPlan return first execution result. Is it supposed to return last execution result? the first execution result as exec_status doesn't make sense.

TestLink version is 1.9.5 TestLink-API-Python-client is 0.4.7

Thanks.

[lczub]

Hello chen2lian4, I could reproduce your problem with the example data, created by TestLinkExample.py and two additional manual executions on test plan 'TestPlan_API A' for test case 'TESTCASE_AA' in TL 199 + TL-API-Py v047.

But I currently see no possibility, to changes this behaviour of getTestCaseForTestPlan on the client site. Comment in xmlrpc.class.php ( TL 199) for this api function is:

   * getTestCasesForTestPlan
   * List test cases linked to a test plan
   * 
   * @param struct $args
   * @param string $args["devKey"]
   * @param int $args["testplanid"]
   * @param int $args["testcaseid"] - optional
   * @param int $args["buildid"] - optional
   * @param int $args["keywordid"] - optional mutual exclusive with $args["keywords"]
   * @param int $args["keywords"] - optional  mutual exclusive with $args["keywordid"]
   *
   * @param boolean $args["executed"] - optional
   * @param int $args["$assignedto"] - optional
   * @param string $args["executestatus"] - optional
   * @param array $args["executiontype"] - optional
   * @param array $args["getstepinfo"] - optional - default false
   * @param string $args["details"] - optional 
   *                  'full': (default) get summary,steps,expected_results,test suite name
   *                   'simple':
   *                   'details':
   * @return mixed $resultInfo

I hope I could give you till the end of this week some more details Greetings Luiko

[chen2liang4]

I understand that that's TestLink problem. Anyway, this client DOES reduce my efforts. Thanks for your contribution.

[lczub]

Hello chen2lian4, I have open a request against TL, see http://mantis.testlink.org/view.php?id=6159 Problem is, that the TL development could not reproduce this failure. I retry my test against the TL 199 demo project (http://demo.testlink.org/) and this works although correct.

My question: which database (mysql, ora, postgre...) and version uses your TL installation? Greetings Luiko

[chen2liang4]

Hi lczub,

The database is MS SQL Server 2012. I read through your request and all notes. I'll try to update TL to 199 and test against.

Thanks

[chen2liang4]

After reading updating comments of TL mantis 6159, since TL dev had reproduced the issue, so I saved time to test with TL 199 against MSSQL 2012. Close this issue, it's not the problem of this project indeed.

Thanks