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

Testnames not working together with suites in suite #2709

Closed
7 tasks
martinaldrin opened this issue Jan 11, 2022 · 4 comments · Fixed by #2712
Closed
7 tasks

Testnames not working together with suites in suite #2709

martinaldrin opened this issue Jan 11, 2022 · 4 comments · Fixed by #2712

Comments

@martinaldrin
Copy link

martinaldrin commented Jan 11, 2022

Hi,

I did a uplift yesterday and today many loops started to fail due missing functionality from our own fork.
Feature was supposed to be included in TestNg in this commit, but something has changed since this commit was merged.
3e14c7d

07:12:50.792 [main] ERROR org.testng.TestNG -
The test(s) <[test1,test2,test3]> cannot be found.

TestNG Version

broken in TestNg 7.5 works in 7.4
#2532 breaks the testname support for suites in suite

Expected behavior

Actual behavior

Is the issue reproducible on runner?

  • Shell
  • Maven
  • Gradle
  • Ant
  • Eclipse
  • IntelliJ
  • NetBeans

Test case sample

I will try to reproduce the fault in a small test, updates are coming.

Contribution guidelines

Incase you plan to raise a pull request to fix this issue, please make sure you refer our Contributing section for detailed set of steps.

@martinaldrin martinaldrin changed the title New behaviour in TestNg 7.5 New behaviour in TestNg 7.5, the feature -testnames do no longer work with suites in suite. Jan 11, 2022
@martinaldrin martinaldrin changed the title New behaviour in TestNg 7.5, the feature -testnames do no longer work with suites in suite. Testnames can not handle suites in suite Jan 11, 2022
martinaldrin pushed a commit to martinaldrin/testng that referenced this issue Jan 11, 2022
@martinaldrin
Copy link
Author

Relates to this commit
#1635

@martinaldrin
Copy link
Author

It looks like #2532 is the root cause for this issue. Support for suites in suite together with testnames are broken from this commit.

@martinaldrin martinaldrin changed the title Testnames can not handle suites in suite Testnames not working together with suites in suite Jan 12, 2022
@martinaldrin
Copy link
Author

PullRequest is created to solve the issue

@juherr juherr linked a pull request Jan 13, 2022 that will close this issue
3 tasks
@krmahadevan
Copy link
Member

@martinaldrin - Can you please help edit this issue and add some context around what is the use case wherein this bug is being seen? That would help us backtrack to the issue in the future if needed from the PR/commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants