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

Allure result json doesn't contain any indication of group annotation when running a test which is executed as gradle task #106

Open
1 task done
danbarel78 opened this issue Mar 27, 2023 · 0 comments

Comments

@danbarel78
Copy link

I'm submitting a

  • bug report

What is the current behavior?

I am trying to run a test written in Java under testng framework and trying to generate an allure report using allure gradle plugin added in my fw.
Now the test has an annotation added, but when running the tests the report that is generated doesn't contain any information about the annotation.
for instance:

@test (groups = {"myGeneratedGroup}, priority = 1)"

when looking at the results generated file (json) , I see no reference to the above annotation

here are the information added to "build.gradle" file

buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath "io.qameta.allure:allure-gradle:2.8.1"
}
}

plugins {
id 'org.springframework.boot' version '2.6.6'
id 'io.spring.dependency-management' version '1.0.11.RELEASE'
id 'java-library'
id 'maven-publish'
// id 'io.qameta.allure' version '2.8.0'
id 'io.qameta.allure-adapter' version '2.11.2'
}
allure {
version = '2.19.0'
autoconfigure = true
useTestNG {

}
adapter {
    frameworks {
        testng {
            autoconfigureListeners.set(true)
        }
    }
}

}
dependencies {
implementation 'org.springframework.boot:spring-boot-starter-actuator'
implementation 'io.micrometer:micrometer-registry-prometheus'
implementation 'org.springframework.boot:spring-boot-starter-web'
implementation 'org.springframework.cloud:spring-cloud-starter-netflix-eureka-client'
implementation 'jakarta.xml.bind:jakarta.xml.bind-api'
testImplementation 'org.springframework.boot:spring-boot-starter-test'
//implementation 'io.qameta.allure:allure-gradle'
//implementation 'io.qameta.allure:allure-adapter'

compileOnly 'org.projectlombok:lombok'
annotationProcessor 'org.projectlombok:lombok'

implementation dep.manager.get3rdCoord("jackson")
testImplementation dep.manager.get3rdCoord("assertj")
implementation dep.manager.get3rdCoord("springdoc-openapi-ui")
runtimeOnly dep.manager.get3rdCoord("jaxb-ri")

implementation dep.manager.getAmatCoord("QAutomationReporting", "DatabaseImpl")
implementation dep.manager.getAmatCoord("QTestAutomationUtils", "InternalUtils")
implementation dep.manager.getAmatCoord("QAutomationReporting", "TestCore")

}

configurations {
testCompile
}

dependencyManagement {
imports {
mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
}
}

What is the expected behavior?

when opening the results json file under labels have new key value parameters
"lables" : [
{
"name": "groups",
"value": "myGeneratedGroup"
},
{
"name": "priority",
"value": "1"
}
]

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath "io.qameta.allure:allure-gradle:2.8.1"
}
}

plugins {
id 'org.springframework.boot' version '2.6.6'
id 'io.spring.dependency-management' version '1.0.11.RELEASE'
id 'java-library'
id 'maven-publish'
// id 'io.qameta.allure' version '2.8.0'
id 'io.qameta.allure-adapter' version '2.11.2'
}

Other information

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

1 participant