XMLRPC extension Proposal: assignTestCaseExecution

[Thilo Fromm]

Hello TestLink community,

I'm Thilo of ProfitBricks; we're using TestLink for internal test planning and coordination. First and foremost - thanks to all of you for your great work! 

Since I'm pretty new to TestLink development I started this thread in order to get an overall orientation on how to approach my improvement request implementation-wise. I'm planning to create an issue in testlink.org's Mantis bug tracker before I do some actual coding; as soon as the details are clear enough to me to actually write a ticket, that is.

We're currently in the process of automating most of our tests, and, in fact, most of our testing and deployment procedures. This includes auto-generating builds via the xmlrpc API, auto-reporting test case execution results, and so on. While driving automation to the maximum possible we ran into some restrictions concerning the xmlrpc API. This thread will discuss one extension we feel is feasible at this time. I'll start a second thread for another extension we're planning to implement.

RATIONALE - assignTestCaseExecution

We noted that there is no possibility to assign test case execution of a specific build via xmlrpc. So after we (auto-)created a build and (auto-)executed the test cases for that build (which happen to not be assigned to any user), we would not get the test results displayed. In order to completely automate build and execution, we would like to propose an API extension, assignTestCaseExecution.

assignTestCaseExecution would take Test Project, Test Plan, Test Case ID, and user name arguments, and would assign this specific execution of the corresponding test case to the user specified.

I'll open this for discussion now. Any feedback, comments, improvements, remarks, and criticism is welcome.

Regards,

Thilo

[Thilo Fromm]

Whoops, I missed something.

assignTestCaseExecution would take Test Project, Test Plan, Test Case ID, and user name arguments, and would assign this specific execution of the corresponding test case to the user specified.

Actually, it would also need the Build this test case is being executed in. So it's

assignTestCaseExecution ( Test Project, Test Plan, Test Case ID, Build name, user name )

[Francisco Mancardi]

Please open issue on Mantis with this text (the part AFTER RATIONALE),
we will continue discussion there.
Thanks a lot

Quick notes:

Full coordinate to assign execution task is made of all these pieces

TestPlan ID + PlatformID (if any exists, otherwise 0) + Build ID + Test
Case ID + User ID

all ID => DATABASE ID


Francisco Mancardi
TestLink Team Leader

> --
> You received this message because you are subscribed to the Google
> Groups "testlink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to testlink-dev...@googlegroups.com.
> To post to this group, send email to testli...@googlegroups.com.
> Visit this group at http://groups.google.com/group/testlink-dev?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Thilo Fromm]

Hi Francisco,

thanks for your response.

Please open issue on Mantis with this text (the part AFTER RATIONALE),
we will continue discussion there.

I've created http://mantis.testlink.org/view.php?id=5670 for this.My Mantis role "reporter", however, does not allow me to assign the issue to me currently.

 

Quick notes:

Full coordinate to assign execution task is made of all these pieces

TestPlan ID + PlatformID (if any exists, otherwise 0) + Build ID + Test
Case ID + User ID

all ID => DATABASE ID

Oh, I missed the platform. Added it to the Mantis issue. Concerning the DB IDs, actually, I would prefer using public names (strings), and translate those to IDs on the server side. I feel this would make writing API clients a lot easier.

Regards,

Thilo

[Francisco Mancardi]

You can not assign issue to you,and is OK this way

>> Concerning the DB IDs, actually, I would prefer using public names (strings), and translate those to IDs on the server side. I feel >> this would make writing API clients a lot easier.

we can discuss this on mantis