[JIRA] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Title: Message Title Keith Jacobs commented on JENKINS-22506 Re: HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Sounds good. Yeah, the details have always displayed for the build type "Execute HP functional tests from HP ALM". The newer build type for Lab Management has never displayed the details. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Title: Message Title Keith Jacobs updated an issue Jenkins / JENKINS-22506 HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Change By: Keith Jacobs Attachment: Build_LabMgmt.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Title: Message Title Keith Jacobs updated an issue Jenkins / JENKINS-22506 HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Change By: Keith Jacobs Attachment: Failed_LabMgmt.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Title: Message Title Keith Jacobs commented on JENKINS-22506 Re: HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Please see attachments. 1. Build_LabMgmt.png: Shows our settings for the job, including the "Execute HP tests using HP ALM Lab Management" build step and the "Publish HP tests result" Post-build action. 2. Failed_LabMgmt.png: Shows what displays in Jenkins for a failed test. The Error Message section shows "Error: Failed." as expected, but instead of showing the text from our Reporter statements in our QTP code, it shows a URL for looking at the run results in ALM. 3. Failed_NonLabMgmt.png: Shows what used to display in Jenkins for a failed test before we moved to Lab Management. The Error Message section shows "Error: Failed." as expected, but we could also see the text from our Reporter statements, instead of having to log into ALM. Your screen shot is showing "Error: No Run". You won't see the URL in the Error Details until you run a job that actually executes a test having Reporter statements. We last tested this issue with version 3.0.7 of the plug-in. Thanks for your help. Keith Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Title: Message Title Keith Jacobs updated an issue Jenkins / JENKINS-22506 HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Change By: Keith Jacobs Attachment: Failed_NonLabMgmt.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Title: Message Title Keith Jacobs commented on JENKINS-22506 Re: HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details We already have a "Publish HP tests result" step in the Post-build actions. See attachment. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Title: Message Title Keith Jacobs updated an issue Jenkins / JENKINS-22506 HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Change By: Keith Jacobs Attachment: publish_screenshot.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-23402) HP ALM Tools Plug-In Returns Error Cannot append QCSession cookies for “Execute HP tests using HP ALM Lab Management” Build Step
Keith Jacobs created JENKINS-23402 HP ALM Tools Plug-In Returns Error Cannot append QCSession cookies for “Execute HP tests using HP ALM Lab Management” Build Step Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 11/Jun/14 1:19 PM Description: Getting the error message "Failed to execute ALM tests. Cause: Cannot appned QCSession cookies" when attempting to execute the build step "Execute HP tests using HP ALM Lab Management" against plug-in version 3.0.5. Version 2.0.2 of the plug-in does not have this issue. Our version of ALM is 11.52, Patch 02. Note: the word "append" is spelled incorrectly in the error message, i.e., that is not a typo here. Full text from console output with version 3.0.5: Started by user anonymous Building in workspace c:\qa\jenkins\jobs\Regression_Test\workspace Logged in successfully to ALM Server http://qc.prod.com/qcbin/ using test_user Failed to execute ALM tests. Cause: Cannot appned QCSession cookies Full text from console output with version 2.0.2: Started by timer Building in workspace c:\qa\jenkins\jobs\Regression_Test\workspace Logged in successfully to ALM Server http://qc.prod.com/qcbin/ using test_user Executing TEST_SET ID: 1596 in TEST_DOM/Test_Proj Description: TEST_SET run report for run id 1089 is at: http://qc.prod.com/qcbin/webui/alm/TEST_DOM/Test_Proj/lab/index.jsp?processRunId=1089 Polling... Run id: 1089 Timeslot id: 2710 Other Notes: 1. Failure occurs with (1) a brand new job, (2) a new job created as a copy of an existing job, and (3) an existing job. 2. Build step "Execute HP functional tests from HP ALM" works just fine. 3. The issue is specific to the build step "Execute HP tests using HP ALM Lab Management". Project: Jenkins Labels: plugin Priority: Major Reporter: Keith Jacobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Keith Jacobs created JENKINS-22506 HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 04/Apr/14 2:22 PM Description: Based on the user guide and current behavior for the HP ALM Tools plug-in, it appears that the plug-in is moving away from displaying detailed information for failed tests directly in Jenkins, and instead simply provides an ALM URL to view results for the test instance. Previously, when viewing test results in Jenkins, the failed test instances displayed the actual Reporter output information from the automated scripts. Now, the test results for the failed tests simply point the user to an ALM URL with the format "td://Project.Domain.qcserver/qcbin/TestRuns?EntityLogicalName=runEntityID=run_id" The URL is not clickable. It must be pasted into a browser. However, that is not our main concern. We have developers who want to see the results directly in Jenkins without having to log into ALM. It appears that the build option to "Running Tests Sets from ALM" is still showing Reporter statements, but the build option to "Run Server Side tests using HP ALM Lab Management" is just showing the ALM URL. We would like an option to have the Reporter statement details displayed in our test results. Project: Jenkins Priority: Major Reporter: Keith Jacobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-22491) HP ALM Tools Plug-In Restricts Results to 100 Test Cases When Using ALM Lab Management
Keith Jacobs created JENKINS-22491 HP ALM Tools Plug-In Restricts Results to 100 Test Cases When Using ALM Lab Management Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Attachments: Jenkins_LabMgmt.png, Jenkins_NonLabMgmt.png, Jenkins_TestResults.png Components: hp-application-automation-tools-plugin Created: 03/Apr/14 6:26 PM Description: After setting up a new HP ALM Lab Management build in Jenkins, a test set containing 127 tests executes completely, but the results only display in Jenkins for 100 test cases. We confirmed within ALM that all 127 tests executed. Note: It is not the first 100 test cases executed. The first test case executed is written to the results, and so is the last test case. For comparison, we also set up a standard "HP tests from HP ALM" build in Jenkins. This is non-Lab Management. The results displayed all 127 tests within Jenkins. The only obvious difference between the two builds is the build type ... the first is Lab Management, and the second is not Lab Management. The reason for the number of test case results being limited to 100 tests appears to be related to how the HP plug-in is writing the results to XML files. Two files (junitResult.xml and Resultstimestamp.xml) are written during test execution. Both files only contain results for 100 tests, instead of all 127 tests. junitResult.xml resides in "\jenkins\jobs\job_name\builds\build_num\". Each test case is written to the node "resultsuitessuitecasescasetestName". There are only 100 of these nodes in the file. Resultstimestamp.xml resides in "\jenkins\jobs\job_name\workspace\". Each test case is written to the node "testsuitestestsuitetestcase". There are only 100 of these nodes in the file. Attachments: 1. Jenkins_LabMgmt.png - shows the header within Jenkins for the build. The build type is "HP tests using HP ALM Lab Management". This is the build type that limits results to 100 test cases. 2. Jenkins_NonLabMgmt.png - shows the header within Jenkins for the build. The build type is "HP tests from HP ALM". This is the build type that does not limit results. 3. Jenkins_TestResults.png - this is the header for the Test Results page. It shows that the results for only 100 tests are displayed. Project: Jenkins Priority: Major Reporter: Keith Jacobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-21897) Execution status: Error, Message: Access is denied
Keith Jacobs commented on JENKINS-21897 Execution status: Error, Message: Access is denied We recently ran into this "Access is denied" issue. Jenkins had been working fine, but we decided to clone our Jenkins VM, so we could build another Jenkins instance. After the clone, we received the "Access is denied" message on the original Jenkins instance. So, we tried to log into the Jenkins VM, and we received the error "The security database on the server does not have a computer account for this workstation trust relationship." Apparently, the cloning process had changed something about the DNS configuration. I don't know what exactly changed, but once the DNS conflict was resolved by our Sys Admin team, we were able to use Jenkins again. Not sure if your case is the same issue, but might be worth trying to login directly to the Jenkins server to see if any errors display. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-21986) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration
Keith Jacobs created JENKINS-21986 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 27/Feb/14 8:43 PM Description: Refer to AlmTestSetsRunner.cs file located here: https://github.com/jenkinsci/hp-application-automation-tools-plugin/blob/master/HpToolsLauncher/Runners/AlmTestSetsRunner.cs The issue is in the RunTestSet function. 1. Before running the test set, a stopwatch timer variable testSw is initialized to null. Line 529. 2. A While loop then runs through each test instance in the test set. The While loop is on line 548. a. Before each test instance is executed, the stopwatch is started, and that testSw variable is set to “Stopwatch.StartNew()”. This occurs on line 595. 3. Unfortunately, as each test instance is completed, the current value of the stopwatch is not saved/stored. a. The stopwatch is reset, the next test instance starts, and the previous stopwatch value is lost. 4. When the last test instance in the test set is completed, the code exits the While loop. a. At that point, the testSw variable contains the duration of the last test instance. b. For our test run, the last test instance took 4 minutes 20 seconds. 5. Next, on line 655, the code loops through all test instances to consolidate information for each test instance. a. The Runtime for each test instance is set to testSw.Elapsed on line 672. b. Remember, that the testSw value is currently set to the duration of the last test instance … 4 minutes 20 seconds for our example. c. Also, remember that the stopwatch is still running. A stop command was never executed. d. So, the duration for the first test instance is actually getting set to the duration of the last test instance. e. Each subsequent test instance duration is getting set to the duration of the last test instance plus some small additional time because the stopwatch is still running and updating testSw. f. That explains why our durations start at 4 minutes 20 seconds, and gradually increase to 4 minutes 48 seconds. It took 28 seconds to loop through the test instances in this FOR loop. 6. The incorrect Total Runtime in the upper right corner of the All Tests page is just the sum of these incorrect test instance durations. a. Fix the test instance problem, and the Total Runtime problem will automatically be fixed. This code needs an update to fix this test duration issue. Thanks, Keith Project: Jenkins Labels: plugin git jenkins Priority: Major Reporter: Keith Jacobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-21987) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter
Keith Jacobs created JENKINS-21987 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 27/Feb/14 8:55 PM Description: Refer to AlmTestSetsRunner.cs file located here: https://github.com/jenkinsci/hp-application-automation-tools-plugin/blob/master/HpToolsLauncher/Runners/AlmTestSetsRunner.cs The issue is in the RunTestSet function. 1. The While loop (line 548) that iterates through all test instances, does a comparison between the elapsed "minutes" and compares it to the timeout value, which we set to a specific number of "seconds". a. Code: while ((tsExecutionFinished == false) (timeout == -1 || sw.Elapsed.TotalMinutes timeout)) b. So, if you currently have the timeout set to 14400, it won’t timeout for 14400 minutes, rather than 4 hours. 2. The obvious workaround would be to just set the timeout value to 240 to achieve the 4-hour timeout. However, there is an IF condition (line 645)that is checked before consolidating results and generating the XML reports. It compares the elapsed time in "seconds" to the timeout value. a. Code: if (timeout == -1 || sw.Elapsed.TotalSeconds timeout) b. So, if you set the timeout to 240, and the test set runs longer than 240 seconds (4 minutes), the XML reports won’t be generated, and the run will be cancelled/aborted. So, basically, timeouts will not be functional in the current version of the hp-application-automation-tools-plugin until this code is fixed. I'm open to the timeout being either minutes or seconds. I just need consistency between these two comparisons. Funny, but if you look at the comments in the code on line 371, it reads "/// param name="timeout"-1 for unlimited, or number of miliseconds/param". So, whoever wrote that code thought the timeout should be in milliseconds. Thanks, Keith Project: Jenkins Labels: plugin jenkins git Priority: Major Reporter: Keith Jacobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
