Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use of "appcenter test run uitest ... --merge-nunit-xml blah.xml" results in error #1208

Closed
jmegner opened this issue Jan 10, 2021 · 3 comments
Labels

Comments

@jmegner
Copy link

jmegner commented Jan 10, 2021

If I run the following command, it works and I get a nunit_xml_zip.zip containing a nunit report xml file for each device:

appcenter test run uitest `
    --app "JacobEgnerDemos/XamarinPipelineDemo" `
    --app-path (gci -Recurse "..\*Signed.apk")[0].FullName `
    --devices "JacobEgnerDemos/two_devices" `
    --test-series "master" `
    --locale "en_US" `
    --build-dir "..\XamarinPipelineDemo.UITest\bin\Release" `
    --uitest-tools-dir "..\XamarinPipelineDemo.UITest\bin\Release" `
    --test-output-dir "." `

If I add --merge-nunit-xml "AppCenterUiTestResult.xml" to the command, I still get the zip file containing device-specific xml files but I also get this error message:

Error: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received an instance of Document

Further error details: For help, please send both the reported error above and the following environment information to us by going to https://appcenter.ms/apps and opening a support ticket (using the help menu in the upper right corner of the screen)


    Environment: win32
    App Upload Id: JacobEgnerDemos/XamarinPipelineDemo
    Timestamp: 1610245258160
    Operation: RunUITestsCommand
    Exit Code: 3
    User Email: [redacted]
    User Name: JacobEgner
    User Id: [redacted]

I was hoping the --merge-nunit-xml argument would get me a single merged xml file.

@Naweap
Copy link

Naweap commented Jan 25, 2022

Got exactly the same issue !

@AnatolyPristensky
Copy link
Contributor

Hello @Naweap,
I've contacted appropriate team and bug has been confirmed.
We will update status of this issue once get results.

@AnatolyPristensky
Copy link
Contributor

Fixed in release 2.10.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants