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

fitnesse-results not generated with Allure #7

Open
Patje1970 opened this issue Apr 18, 2019 · 6 comments
Open

fitnesse-results not generated with Allure #7

Patje1970 opened this issue Apr 18, 2019 · 6 comments

Comments

@Patje1970
Copy link

Patje1970 commented Apr 18, 2019

We have been trying to get Allure working with Fitnesse. Using the several info's available here, for example: https://github.com/fhoeben/allure-fitnesse-listener/blob/master/README.md
Almost everything seems to work, except the following.

When I generate a report, it will not show any report.
After some researching and more testing I see when a generate a report, that there is no file fitnesse-results generated. So I guess that is why I get no results on a page but a blank page after I give the command Allure open. Can you tell me how I get the fitnesse-results file into the allure-report file?

I need to add we are using the Xebium version for Fitnesse.
With that Fitnesse puts the original testresults in a file called testResults, not fitnesseResults. (Xebium\FitNesseRoot\files\testResults)

Hope someone can help me figure this out.

@tcnh
Copy link
Collaborator

tcnh commented Apr 18, 2019

If I understand it correctly, your issue is that the fitnesse result htmls are not copied in the allure report?

If that's the case: this is because the listener expects the results in the fitnesse-results folder (The listener was built with HsacFitnesseRunner in mind, because it generates more or less standalone html report pages and junit xml output per page.)

How do you run your tests? maybe some simple changes to the listener will be enough to suit your needs.

@Patje1970
Copy link
Author

Thank you for your reply.
We run the tests with Xebium and are using the version of Fitnesse version 20171212 with that.

This is part of our POM about Allure/Fitnesse.

${project.build.directory}\allure-results ${project.build.directory}\allure-report nl.hsac.fitnesse.junit.allure.JUnitAllureFrameworkListener nl.hsac allure-fitnesse-listener 1.0.3 test

copy-resources
site

copy-resources


${allure.report.directory}\fitnesseResults


${project.build.directory}\allure-results\fitnesseResults true


ru.yandex.qatools.allure allure-maven-plugin 2.5 allure-results ${allure.report.directory}

I hope you can help with this information. I will look into the listener as well.

@tcnh
Copy link
Collaborator

tcnh commented Apr 23, 2019

can you paste the xml as a snippet?

@Patje1970
Copy link
Author

image

image

image

image

@Patje1970
Copy link
Author

These are the snippets.

@tcnh
Copy link
Collaborator

tcnh commented Apr 25, 2019

Assuming you're using hsac fitnesse runner and generate fitnesse html reports in target\fitnesse-results, can you try it using the newer maven plugin:

  <reporting>
	<excludeDefaults>true</excludeDefaults>
	<plugins>
	<plugin>
		<groupId>io.qameta.allure</groupId>
		<artifactId>allure-maven</artifactId>
		<version>2.10.0</version>
		<configuration>
			<resultsDirectory>allure-results</resultsDirectory>
			<reportDirectory>${allure.report.directory}</reportDirectory>
			<reportVersion>2.10.0</reportVersion>
		</configuration>
	</plugin>
	</plugins>
</reporting>

and set the output directory to allure's report directory/data for the fitnesse result html's:

 <execution>
	<id>copy-resources</id>
	<phase>site</phase>
	<goals>
		 <goal>copy-resources</goal>
	</goals>
	<configuration>                                   
	   <outputDirectory>${allure.report.directory}/data/fitnesseResults</outputDirectory>
	   <resources>
		  <resource>
			  <directory>${project.build.directory}/fitnesse-results</directory>
			  <filtering>true</filtering>
		  </resource>
		 </resources>
	</configuration>
</execution>

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

No branches or pull requests

2 participants