-
Notifications
You must be signed in to change notification settings - Fork 64
Custom field calls need the tcaseversion_id and not the version number #88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hello Roel, I'm sorry, but your suggestion produces tracebacks in my environment:
I changed following for the test in TestLinkExample_CF_KW.py results are So for my environment, using the tc version number works, using the the tc version id not. If you take a look into the TL php code xmlrpc.class.php - getTestCaseCustomFieldExecutionValue, you find the sql statement which shows, that the TL php server really requires the version number as input. To understand your failure situation, it would be helpful, if you can send the original failure messages before (without) your code changes (and maybe also the logs for the TestLinkExample.py plus TestLinkExample_CF_KW.py examples ). Regards Luiko |
|
Hi, Weird. I'm using testlink 1.9.13. As requested: Results in: and results in So both calls work for me, only the one as described in the your example results in an empty value field. |
|
It's indeed a bug on testlink API itself, which has been resolved in the latest version: |
|
Hello Roel, good to here, that you find the reason for this failure. Cheers Luiko |
Example is wrong:
Custom field calls need the tcversion_id and not the version number (line 235)
(as a plus, my vim configuration removed unwanted spaces)