[
https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159752#comment-159752
]
Bruno P. Kinoshita commented on JENKINS-12810:
----------------------------------------------
Hi Jaroslavas
> Why plugin should seek for platform option in XML?
That's because a plan has many platforms. Let's say you have a test plan with
two platforms. Now the plug-in *must* always include the platform ID or the
platform name when invoking TestLink XML-RPC API methods. Otherwise an error is
raised by TestLink.
> There's no test plan option in generated JUnit/TestNG XMLs, but no problem
> for plugin to find TC only from defined Test Plan.
That's a good argument :D
But here's no way to include the platform in the job configuration screen
(imagine a scenario with 20 platforms). The platform is linked to the test
case, and not to the test project (like test plan). Below I tried to represent
how is the relation of each entity more or less (omitted test case version for
simplicity)
test project -> has many -> test plan -> has many -> test case -> has one ->
platform
..................................... -> has many -> platform
> Thank You, Bruno, for productive communication! And sorry for my silly
> questions.
I really enjoy having this type of conversation Jaroslavas. And no need for
sorry your questions are very good.
> I'm not really programer guy - I'm tester. So, my point of view to problem
> may be different
That's why it's so important that you participate in the project. Each time a
user like you propose a new feature, find a bug, or just has a cool
conversation like this, the plug-in gets better and more useful for testers,
developers, devops and so it goes.
This weekend I think I will have the first release candidate for 3.1, with all
the issues found during alpha test fixed, as well as the release check list
done (https://wiki.jenkins-ci.org/display/JENKINS/Release+check+list). I also
want to include all the alpha testers in the plug-in team as contributors
(unless they prefer remain anonymous :)
Cheers
Bruno
> JUnit test results are getting wrongly attached to all the test cases
> ---------------------------------------------------------------------
>
> Key: JENKINS-12810
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12810
> Project: Jenkins
> Issue Type: Bug
> Components: testlink
> Affects Versions: current
> Reporter: Vignesh Senapathy
> Assignee: Bruno P. Kinoshita
> Fix For: current
>
> Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, schema.jpg,
> screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png,
> testlink-3.1-alpha2.hpi
>
>
> Hi,
> I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the
> Junit Test results are getting generated. This in turn calls the Testlink xml
> rpc and attaches the results to the test case, but the test results are
> attached wrongly. The 1st test case has 6 results, the next has 5 and so on
> and the last one has 1 test result attached to it. I dont know if it is bug
> which is causing this. Please let me know what seems to be the problems. Also
> the execution flags are correctly rendered in this. which ever test case
> fails is marked as failed and which passed is marked as passed.
> Also I have one custom field which maps to the test suite name and test
> classname.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
