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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • testlink-plugin
    • Jenkins 1.650
      Testlink plugin 3.13
      TestLink 1.9.16

      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.

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

              Created:
              Updated: