I am trying to generate the allure reports , with specflow.json configuration
and the sample test case with tags
I don't see the "packages" in allure report are generating as hierarchy , can someone please help
There is an open PR on this issue here.
https://github.com/unickq/allure-nunit/pull/38
Related
I feel like I'm missing something obvious, but I haven't found an answer anywhere else.
I have set up Allure as described in the documentation for NUnit 3. After I run my tests through the VS Test Runner I can see the result.json and attachment.txt files in my allure-results directory, but I don't understand how this translates into the actual Allure report, shown at https://raw.githubusercontent.com/unickq/allure-nunit/master/AllureScreen.png.
I added a build step for my project in teamcity which consists on using the plugin Parasoft Findings to publish an XML report of all the code violations. the problem is that teamcity is failing to parse XML report. It says there is an unexpected report format and to see log (which I couldn't find).
I already checked the report location pattern which is right. I don't use SOAtest but C++ test so I only put "Parasof analyzers 10.x" for the report type
I'm sorry but you did not provide any additional details regarding your question and it's hard to help you.
Please, provide:
error message
your configuration of build step and version of TeamCity and C++test
command line used to start C++test ( if you are using variables,
replace variables with real values used in your run)
By log I think, you should check your build step log, and provide us the right content.
You can find such logs on two different ways:
You can download it by clicking "Download full build log" on build
log page (Recommended).
Try to find the raw output from the build agent by looking in the
agents logs directory, for example in
c:\TeamCity_dir_agent\logs\teamcity-build.log
Following article from JetBrains' TeamCity manual might good point to start
Edit:
Parasoft updated the plugin which fixed the issue:
https://plugins.jetbrains.com/plugin/9949-parasoft-findings
I have the same issue. Error messages in build log:
Unexpected report format: <path-to>\report.xml. See log for details.
Failed to parse XML report
Failed to parse XML report
Step test results (Parasoft Findings) failed
teamcity-agent.log and teamcity-build.log are having no entries within this build step because there is no piece of code which would write that into during this error case.
Edit/Workaround:
In the report the node <ExecutedTestsDetails> must be below the node <Exec>. The node still has the right indendation but it is at the same level as <Exec>. The xsl of TeamCity Plugin works perfectly if you fix the report xml manually.
To make it work you can add the Build Feature "File Content Replacer" like that:
Regex: (?s)(<ExecutedTestsDetails.*?<\/ExecutedTestsDetails>).*?(<Exec.*?>)
Replace with: $2 $1
How do I integrate a html test results report generated by karma-htmlfile-reporter with VSTS build summary section? Any inputs will help
There is no build-in way to achieve your requirement.
You could create your own extension to display graphical content (HTML page) in my VSTS/TFS summary page.
For example add a custom section in build result through your extension, with this way, you can add html test results report in that custom section.
There is the sample about build result extension: vsts-extension-samples
More information about how to build extension, you can refer to this article
Create your first extension for Visual Studio Team Services
A extension for your reference Publish HTML Artifact
Update
Find another workaround, according to below reply in this question:
VSTS Code coverage supports the outputted code coverage results in
Jacoco or Cobertura formats. Karma-Coverage supports Cobertura
format.
Edit your karma.config.js for ....
Once you configure the output format, you could try to use Publish Code Coverage task to upload code coverage data to VSTS.
TFS can understand a report if it is in the format of a format called TRX.
This can be achieved by using the karma-trx-reporter plugin in the karma.conf.js
Once the report is generated, we can then use MSTest to publish the results
or you can upload using the VSTS workflow function
After using the install guide provided by Chon I wasn't able to edit any report. The error I'm getting is
Description Resource Path Location Type The library with the namespace
"MaximoSystemLibrary" is not
found. poprint.rptdesign /MaximoReport/PO line 2 Report Problem
I already tried solutions explained by Cherin in his answer here
Please verify that the MaximoSystemLibrary is located in the Libraries folder of your Workspace.
/Workspace/libraries/MaximoSystemLibrary.rptlibrary
I am facing a problem with Hudson and NUnit testing. When trying to publish the Test Result Report for NUnit, the option in Hudson, i.e., "Publish NUnit Test Result Reports", is creating a problem. I am unable to provide the Path of the already-created XML file under the workspace folder of the Job. When I set the path of my file, i.e., "nunit-result.xml" and run the job, it throws an error:
"No test report files were found. Configuration error?"
Can anyone please help me out?
Thanks in advance.
Check the the beginning of the log where the clone is made. Sometimes when you have the "Enable concurrent builds" option it triggers another build in a different workspace called your-project-name#2/source and that's why it can't find the reports