Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53137

Automated cases found, but I cannot find them in job workspace at Jenkins

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      According with job's console output, the plugin finds correctly the project, test plan and automated cases assigned to it, using XML RPC from Testlink server.

       

      Started by user XXXXXXX
      [EnvInject] - Loading node environment variables.
      Building on master in workspace C:\JenkinsWorkspaces\TestLink_Dummy_Test_Job
      Preparing TestLink client API.
      Using TestLink URL: http://XXXXX/testlink/lib/api/xmlrpc/v1/xmlrpc.php
      
      Found 2 automated test cases in TestLink.
      
      Sorting automated test cases by TestLink test plan execution order.
      
      Executing single Build Steps.
      
      Executing iterative Build Steps.
      
      Looking for the test results of TestLink test cases.
      
      Looking for test results in TestNG suites by its name.
      
      Found 2 test result(s).
      
      Finished: SUCCESS
      

       

      But after that, I can't find any file in the job workspace with such case (and scripts) list. All cases has scripts assigned to them using a custom field located at the test case definition level in TestLink.

      According with many tutorials found in google, this list used to be something to be passed to Maven as parameter like "test -DsuiteXmlFile=suite.xml" so I supposed it has to be a file named suite.xml and stored somewhere in the job workspace.

      I'm going to run the case scripts with .NET directly, not Maven, so I need the list of them available in the job workspace.

      Thanks for your attention.

      Regards.

        Attachments

          Activity

          Hide
          hgc2002 herman gomez added a comment -

          I've found that the plugin documentation doesn't say anything about storing the test plan & cases data into any kind of file.

          Having this, I can't explain how the 100% of examples found in google works having the first single step with MAVEN and a parameter -DsuiteFileXml=file.exe - I was supossing this was an input parameter form a standard file coming from testlink plugin. Can somebody explain me this?

          Why this MAVEN step is not an iterative test step ? How does it gets the test case data to execute it ?

          By the way, the plugin wiki does mention ANT as an iterative test step. How and why does MAVEN works differently (and much better) ?

           

          Show
          hgc2002 herman gomez added a comment - I've found that the plugin documentation doesn't say anything about storing the test plan & cases data into any kind of file. Having this, I can't explain how the 100% of examples found in google works having the first single step with MAVEN and a parameter -DsuiteFileXml=file.exe - I was supossing this was an input parameter form a standard file coming from testlink plugin. Can somebody explain me this? Why this MAVEN step is not an iterative test step ? How does it gets the test case data to execute it ? By the way, the plugin wiki does mention ANT as an iterative test step. How and why does MAVEN works differently (and much better) ?  
          Hide
          hgc2002 herman gomez added a comment -

          The current version at github (3.15) does fail too but only if you set something in test plan custom fields space. So, if you don't set anything there, the rest works fine, including list of custom fields (for test cases).

          By the way, I modified the plugin to generate an XML file in the workspace with all data from test plan and test cases specifications, instead of using iterative steps in Jenkins.

          Show
          hgc2002 herman gomez added a comment - The current version at github (3.15) does fail too but only if you set something in test plan custom fields space. So, if you don't set anything there, the rest works fine, including list of custom fields (for test cases). By the way, I modified the plugin to generate an XML file in the workspace with all data from test plan and test cases specifications, instead of using iterative steps in Jenkins.

            People

            • Assignee:
              kinow Bruno P. Kinoshita
              Reporter:
              hgc2002 herman gomez
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: