search

allure-framework / allure-java

Allure integrations for Java test frameworks
Apache License 2.0
354 stars 224 forks source link

🐞: Allure TestOps selective runs doesn't work with TestNG + maven #1023

Closed dismoralzor closed 2 months ago

dismoralzor commented 6 months ago

What happened?

When I run one test from Allure TestOps, all tests are run in Jenkins job, the selective test execution is not working.

What Allure Integration are you using?

allure-testng

What version of Allure Integration you are using?

2.26.0

What version of Allure Report you are using?

2.26.0

Code of Conduct

cheshi-mantu commented 6 months ago

@dismoralzor please follow the community rules and use English only

dismoralzor commented 6 months ago

@cheshi-mantu Oh, sorry sir, this is my first ticket

cheshi-mantu commented 6 months ago

I tried to generate projects from https://allurereport.org/start/ on 2.26.0 for testng and junit5

Junit5 selective test run works fine java17-junit5-maven.zip

TestNG selective test run is not working java17-testng-maven.zip

komissarov-qa-auto commented 3 months ago

@baev Please fix this bug, my team is blocked by this feature (15 peoples) Can your name the deadline for fixing?

slevenet commented 3 months ago

@komissarov-qa-auto Hi, we are going to fix it in the nearest time, until 20th of June

vbragin commented 3 months ago

@dismoralzor @komissarov-qa-auto What allure-testops-jenkins plugin version have you use?

Could you add the following command into your job config and provide an output from it?

cat $ALLURE_TESTPLAN_PATH or you can provide a content of testplan.json in your work dir

/job//ws/.allure-ee/testplan.json
vbragin commented 3 months ago

The problem was in jenkins plugin. Will be fixed in the next release.

komissarov-qa-auto commented 3 months ago

The problem was in jenkins plugin. Will be fixed in the next release.

What are the deadlines? we really need this functional

As I understand it, information from our side is not needed, you have been provided with it

dismoralzor commented 3 months ago

@vbragin, hello! sir, Is the problem solved for allurectl too?

@dismoralzor @komissarov-qa-auto What allure-testops-jenkins plugin version have you use?

allure-testops-jenkins plugin version 3.29.0 allurectl 2.15.1

Could you add the following command into your job config and provide an output from it?

It says that a test plan has been created, but there is no ALLURE_TESTPLAN_PATH variable.

06:11:41  Save test plan for [1] to file [/u01/jenkins_slave/workspace/SWATS/examples/Allure TestOps Upload Testng Maven/.allure/testplan.json]
06:11:51  + printenv
06:11:51  + grep ALLURE_
06:11:51  ALLURE_PROJECT_ID=227
06:11:51  ALLURE_RESULTS=./target/allure-results/
06:11:51  ALLURE_USERNAME=Igor
06:11:51  ALLURE_LAUNCH_TAGS=release
06:11:51  ALLURE_JOB_RUN_ID=761541
06:11:51  ALLURE_TOKEN=****
06:11:51  ALLURE_ENDPOINT=https://testops.omega.ru
06:11:51  ALLURE_LAUNCH_NAME=allurectl test
vbragin commented 3 months ago

@komissarov-qa-auto Try to use 4.0.2 from https://dl.qameta.io/ui/native/bin/allure-testops-jenkins