nicklargen / testcafe-reporter-nunit3 Goto Github PK

🚨 The automated release from the beta branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the beta branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Should it be possible to publish the test attachments with a relative path in Azure DevOps for NUnit3 reports created with the testcafe-reporter-nunit3 reporter?

The task is configured like this:

- task: PublishTestResult@2
   inputs:
     testResultsFormat: 'NUnit'
     testResultsFiles: 'tmp/report.xml'
     publishRunAttachments: true

The report looks like this:

<?xml version="1.0" encoding="UTF-8" ?>
<test-run>
    <test-suite type="Assembly" name="...">
        <-- ... -->
        <test-case name="..." result="Failed" duration="24.161">
            <failure>
                <message>
                    ...
                </message>
                <stack-trace>
                    ...
                </stack-trace>
            </failure>
            <attachments>
                <attachment>
                    <filePath>tmp/screenshots/.../errors/1.png</filePath>
                </attachment>
            </attachments>
        </test-case>
    </test-suite>
</test-run>

It seems that the file can not be found, even tough it is in the given location relative to $(System.DefaultWorkingDirectory):

##[warning]Skipping attachment as it is not available on disk: tmp/screenshots/.../errors/1.png

Should attachment path be absolute? I also tried running it on linux and windows build agents.