question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

'allure-results' folder doesn't create after "mvn clean test" (Java+Junit4, Win 10)

See original GitHub issue

pom.xml:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>1</groupId>
  <artifactId>Millennium</artifactId>
  <version>0.0.1-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>Millennium</name>
  <url>http://maven.apache.org</url>

  <properties>
  	<maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

  <dependencies>
  	<dependency>
    	<groupId>org.seleniumhq.selenium</groupId>
    	<artifactId>selenium-java</artifactId>
    	<version>3.141.59</version>
	</dependency>
	<dependency>
    	<groupId>junit</groupId>
    	<artifactId>junit</artifactId>
    	<version>4.12</version>
    	<scope>test</scope>
	</dependency>
	    <dependency>
        <groupId>io.qameta.allure</groupId>
        <artifactId>allure-junit4</artifactId>
        <version>2.12.1</version>
        <scope>test</scope>
    </dependency>
    <dependency>
    	<groupId>org.apache.commons</groupId>
    	<artifactId>commons-io</artifactId>
    	<version>1.3.2</version>
	</dependency>
    
  </dependencies>
  <build>
    <plugins>
    	<plugin>


    	<groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>3.8.1</version>
            <configuration>
            	<source>1.8</source>
            	<target>1.8</target>
            </configuration>
        </plugin>
        
	<plugin>
    <!--Подключаем Surefire плагин--> 
    	<groupId>org.apache.maven.plugins</groupId>
    	<artifactId>maven-surefire-plugin</artifactId>
	    <version>2.19.1</version>
	    <!--Настраиваем запуск aspectj-->
	    <configuration>
	        <testFailureIgnore>true</testFailureIgnore>
	        <argLine>
	             -javaagent:"${settings.localRepository}/org/aspectj/aspectjweaver/1.9.4/aspectjweaver-1.9.4.jar"
	        </argLine>
	        <properties>
	            <!--Правила для сбора информации Allure, на которые смотрит aspectj при работе-->
	            <property>
	                <name>listener</name>
	                <value>io.qameta.allure.junit4.AllureJunit4</value>
	            </property>
	        </properties>
	        <systemProperties>
	            <!--Результаты Allure складываются в отдельную дирректорию в новом формате-->
	            <property>
	                <name>allure.results.directory</name>
	                <value>${project.build.directory}/target/allure-results</value>
	           </property>
	        </systemProperties>
	    </configuration>
	    <!--Зависимость для aspectj-->
	    <dependencies>
	        <dependency>
	            <groupId>org.aspectj</groupId>
	            <artifactId>aspectjweaver</artifactId>
	            <version>1.9.4</version>
	        </dependency>
	    </dependencies>
		</plugin>
    </plugins>
</build>
</project>

‘allure-results’ folder doesn’t create after “mvn clean test” in target folder. image

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:17 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
fescobarcommented, Aug 21, 2020

@uLucasFraga If you need help, share the structure of your project zipped with empty tests.

1reaction
anca1108commented, Apr 6, 2020

@fescobar thank you for you help. i updated versions of aspectj and allure to latest and it seems to work now.

Read more comments on GitHub >

github_iconTop Results From Across the Web

allure-results directory not generated under target folder
Create a file allure.properties under your test resources (usually it is src/test/resources ) with the following content:
Read more >
Allure reports do not generate results when calling mvn test ...
If I call mvn from the command line and pass in some arguments.... I have no allure-results folder generated, I am very confused....
Read more >
инфраструктура - automated-testing.info
[ERROR] Directory D:\IdeaProjects\testov.net\target\allure-results not found. [WARNING] Allure report was skipped because there is no results ...
Read more >
Allure Framework
Allure Framework is a flexible lightweight multi-language test report tool that not only shows a very concise representation of what have ...
Read more >
Allure Results Directory Path Setup - YouTube
When you execute your tests, the allure results folder is generated in the project root directory. If you want to change the default...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found