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 TestOps selective runs doesn't work with TestNG + maven #1023

Closed
1 task done
dismoralzor opened this issue Mar 26, 2024 · 10 comments
Closed
1 task done
Labels
type:bug Something isn't working

Comments

@dismoralzor
Copy link

dismoralzor commented Mar 26, 2024

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

  • I agree to follow this project's Code of Conduct
@dismoralzor dismoralzor added triage type:bug Something isn't working labels Mar 26, 2024
@cheshi-mantu
Copy link

@dismoralzor please follow the community rules and use English only

@dismoralzor
Copy link
Author

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

@dismoralzor dismoralzor changed the title 🐞: Не работает селективный запуск тестов в Allure TestOps на TestNG + maven 🐞: Allure TestOps selective runs doesn't work with TestNG + maven Mar 26, 2024
@cheshi-mantu
Copy link

cheshi-mantu commented Mar 27, 2024

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
Copy link

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

@slevenet
Copy link

slevenet commented Jun 4, 2024

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

@vbragin
Copy link
Contributor

vbragin commented Jun 18, 2024

@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
Copy link
Contributor

vbragin commented Jun 18, 2024

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

@komissarov-qa-auto
Copy link

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
Copy link
Author

dismoralzor commented Jun 20, 2024

@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
Copy link
Contributor

vbragin commented Jun 20, 2024

@baev baev removed the triage label Jul 30, 2024
@baev baev closed this as completed Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants