Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3538

polarion-uploader cannot process cypress XMLs

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • User Experience
    • None
    • False
    • None
    • False
    • Kiali Sprint #63

      after fixing polarion uploader (see linked jira) remaining work to get valid reports into polarioin is:

      • testcase name and classname must not contain special characters  + - && || ! ( ) { } [ ] ^ " ~ * ? : \
      • test case title in polarion is created like this <testClassName>.<testMethodName> and it's is skipped when it already exists. There are some duplicate entries in the generater junit output - we need to remove duplicate names from test suite

       

      -------------------------------------------

       

      I did investigate XML created by cyperss and reproduced all locally. All works meaning:

      • cypress produces valid XMLs
      • jmx tool concatenate produced XMLs into final, also valid XML
      • no other XML related problems were found
      •  

      Problem is polarion-uploader, specifically pylero tool. It cannot process final XML for unknown reasons. No errors or warning. Nothing. 

      Successful run log is attached. It resulted into creating of the test run, but not created any test cases.  Its possible that Pylero require some specific adjustments for XML tweaking. Putting this effort to side, since there are more possible unknowns.

       -- 
      mochaJunitReporterReporterOptions key in reporter-config.json might help us shape XML to desired state, will try that first and see if it works for polarion uploader
      see docs for more info https://www.npmjs.com/package/mocha-junit-reporter
       -- 
       -- 
      If this will not work, I will investigate other tool, where I do know its working for Cypress results. 

       

      after some more investigation, I find out that the problem lays in the format of XML, specifically the XML cannot contain whitespaces

       

            rhn-support-pmarek Pavel Marek
            rhn-support-pmarek Pavel Marek
            Pavel Marek
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: