lczub / TestLink-API-Python-client

A Python client to use the TestLink API
105 stars 63 forks source link

whatArgs reports incorrect arg name for createTestCase #51

Closed dmcbride64 closed 9 years ago

dmcbride64 commented 9 years ago
whatArgs('createTestCase')

reports the following:

"createTestCase(, , , ,

, [steps=], [precondition s=], [importance=], [execution=], [order=], [internalid=], [che ckduplicatedname=], [actiononduplicatedname=], [devKey=])\n createT estCase: Create a test case\n positional args: testcasename, testsuiteid, testprojectid, authorlogin,\n summary\n optional args : preconditions, importance, execution, order, internalid,\n checkduplicatedname, actiononduplicatedname\n \n argument 'steps' will be set wi th values from .stepsList, \n - when argsOptional does not include a 'steps' item\n - .stepsList can be fi lled before call via .initStep() and .appendStep()\n "

In particular, it says that [execution=<execution>]

However, when using createTestCase with this argument (e.g. execution=2), the test case was not set to 'Automated', as expected, although no error was reported and the test case was successfully created.

After some searching and testing, I found that I could use executiontype instead of execution and I would get the result I was expecting. Note that executiontype is not reported by whatArgs.

So, it seems likely that 'whatArgsis reportingexecutionwhen it should be reportingexecutiontype`

lczub commented 9 years ago

Hello dmcbride64,

thanks for this hint. Your are right, the argument name is executiontype and not execution. Reason for this mistake is a wrong comment in testlink source code

compare comment createTestCase and constants $executionTypeParamName

Your workaround to use executiontype is correct and I will implement it.

Regards Luiko