-
Bug
-
Resolution: Unresolved
-
Major
-
None
Hi,
I've installed the TAP and TestLink plugins in Jenkins, and configured a build following the same logic as many people here (I can post details if needed).
My build seems to run fine in Jenkins, but the problems are after:
1. The build indicates "Not Run" as execution state.
2. The tests status is not updated in TestLink.
I have attached 2 screenshots: ss1.jpg which shows the build status, and ss2.jpg showing the TAP Extended Test Results screen.
Could you please help me finding what's wrong? Thank you in advance.
[JENKINS-20039] TestLink plugin indicates test case as "not run" and TestLink is not updated with build status
Garden Dwarf
added a comment - Hi Bruno,
In the screenshots I posted, it was clear to me that Jenkins finds the results. What I didn't understand is how to reflect those results in Testlink (i.e. transfer of results from Jenkins to Testlink).
If you tell me that Jenkins is not seeing the results, then I do not understand what is going wrong either. Jenkins just executes a scripts which create the result file (status hardcoded, just for test purposes).
Could you please provide help to understand where something is going wrong? Thank you in advance.
Garden Dwarf
added a comment - Hi Bruno,
In the screenshots I posted, it was clear to me that Jenkins finds the results. What I didn't understand is how to reflect those results in Testlink (i.e. transfer of results from Jenkins to Testlink).
If you tell me that Jenkins is not seeing the results, then I do not understand what is going wrong either. Jenkins just executes a scripts which create the result file (status hardcoded, just for test purposes).
Could you please provide help to understand where something is going wrong? Thank you in advance. 
Franck Derunes
added a comment - make sure your tap filename is the same name than your "Key Custom Field" value (in jenkins)
e.g.
testlink custom field name: MY_CUSTOM_FIELD, value = test1
jenkins Key Custom Field: MY_CUSTOM_FIELD
jenkins tap filename: test1.tap
Franck Derunes
added a comment - make sure your tap filename is the same name than your "Key Custom Field" value (in jenkins)
e.g.
testlink custom field name: MY_CUSTOM_FIELD, value = test1
jenkins Key Custom Field: MY_CUSTOM_FIELD
jenkins tap filename: test1.tap
Garden Dwarf
added a comment - I have checked the field names and values as well as file name as indicated, and I see no issue (i.e. seems to be configured correctly).
Could you please post screenshot of Jenkins configuration, Testlink configuration and also one with the information that we should see after a correct build?
Garden Dwarf
added a comment - I have checked the field names and values as well as file name as indicated, and I see no issue (i.e. seems to be configured correctly).
Could you please post screenshot of Jenkins configuration, Testlink configuration and also one with the information that we should see after a correct build? 
nilam khule
added a comment - Hi, Any updates on this bug.
I am facing same issue with following build versions:-
Jenkins:- 1.599
testlink plugin:- 3.10
teslink:- 1.9.13
Due to this issue I am blocked.
nilam khule
added a comment - Hi, Any updates on this bug.
I am facing same issue with following build versions:-
Jenkins:- 1.599
testlink plugin:- 3.10
teslink:- 1.9.13
Due to this issue I am blocked. Garden Dwarf
added a comment - Hi,
I received no help and the issue is still there. Sorry for not being able to help you now Garden. I'll keep busy for the next months due to my relocation, but should you have any pull request we can merge it and cut a new release.
Cheers,
Bruno
Garden Dwarf
added a comment - Hi Bruno,
I've stopped trying to find a solution. My comment was just to answer Nilam about the progress on the issue.
Cheers,
Garden Dwarf
added a comment - Hi Bruno,
I've stopped trying to find a solution. My comment was just to answer Nilam about the progress on the issue.
Cheers, Hi Bruno,
I'm facing the problem like Garden Dwarf.
Jenkins:- 1.642
testlink plugin:- 3.11
teslink:- 1.9.14
Could anyone find a solution to solve that problem ?
Please share me your idea.
Thanks
Garden Dwarf
added a comment - Just to confirm I didn't find a solution. 
Hi Garden, I still can't understand what's wrong. For some reason your test has not been executed in Jenkins (or the plug-in couldn't find its output).
The execution status displayed in the Jenkins UI doesn't reflect the latest execution status of the test in TestLink, but only the latest execution status in that build.
HTH,
Bruno