endless allure2 report loading on firefox

Describe the bug When I try to open the index.html from the /target/site/allure-maven-plugin/index.html. I’ve got an endless loading widgets on the “overview” page (see attachment.) When I go to the “behaviours” page, I’ve got a 404 error page. I’ve the same behaviour on IE-11.0.9600.19356 and Chrome-75.0.3770.142.

A few days ago, there was an update of Firefox on my laptop. My new version is 68.0-Firefox Release-July 9, 2019. I guess the previous version was 67.0. With the previous version of Firefox, there was no error when I opened the local allure web site from the local files.

Morevover, when I launch the server using mvn allure:serve, the report is correctly displayed.

To Reproduce Steps to reproduce the behavior:

1. compile the maven project generating the allure report
2. Open the index.html file of <my_project>/target/site/allure-maven-plugin/ in firefox
3. See error

Expected behavior I need to open the allure report from the generated files without using a running web server. In order to share it with my customer.

Screenshots

Environment (please complete the following information):

Allure version	2.12.1
Test framework	junit.jupiter@5.5.0
Allure adaptor	allure-junit5@2.12.1
Generate report using	allure-maven@2.18

Additional context Below an extract of my pom.xml

</dependencies> .... <dependency> <groupId>io.qameta.allure</groupId> <artifactId>allure-junit5</artifactId> <version>2.12.1</version> </dependency> ... </dependencies>

   <plugins>
        <!-- generate test report-->
        <plugin>
            <groupId>io.qameta.allure</groupId>
            <artifactId>allure-maven</artifactId>
            <version>2.10.0</version>
            <executions>
                <execution>
                    <id>allure-site</id>
                    <phase>verify</phase>
                    <goals>
                        <goal>report</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
        <plugin>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-maven-plugin</artifactId>
        </plugin>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>${maven-surefire-plugin.version}</version>
            <configuration>
                <properties>
                    <property>
                        <name>listener</name>
                        <value>io.qameta.allure.junit5.AllureJunit5</value>
                    </property>
                </properties>
                <includes>
                    <include>**/*Test*.java</include>
                </includes>
                <systemProperties>
                    <property>
                        <name>allure.results.directory</name>
                        <value>${project.basedir}/target/allure-results</value>
                    </property>
                    <property>
                        <name>junit.jupiter.extensions.autodetection.enabled</name>
                        <value>true</value>
                    </property>
                </systemProperties>
                <reportFormat>plain</reportFormat>
            </configuration>

</plugin>

I also try to start chrome using this procedure, without success :

When opening the report from the local file, either open it in Firefox or launch Chrome with the >–allow-file-access-from-files flag. For other browsers, you need to enable cross-origin requests >to local files.

Thank you in advance. Regards.

[e-avtonov]

@frederic-boissiere this can help with report opening in firefox 68: https://stackoverflow.com/questions/56999411/firefox-68-local-files-now-treated-as-cross-origin-is-there-a-way-to-override

[baev]

there are only few options (at least that I know) to make it possible:

1. embed everything into single html file. That will make reports unusable pretty much for everyone who has more than 1000 tests in run. So that could be an option but as opt-in feature
2. use JSONP files instead of JSON. We have in plan to add such support but it requires some deep code changes and only planned for Allure 3 as low priority feature.

for now, you only need such feature for local reports, so you have a few options:

1. use allure command line tool. It provides allure open and allure serve commands to open/serve reports
2. for IDEA users there are open in browser feature (you can find it in context menu of html files) that will start web server for you