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.

Sign up for GitHub

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

Jump to bottom

#3370 Use traditional class pattern scanning for testNG - some tests … #6695

Merged
merged 1 commit into from
Jul 1, 2022
Merged

#3370 Use traditional class pattern scanning for testNG - some tests … #6695

merged 1 commit into from
Jul 1, 2022

Conversation

planetf1
Copy link
Member

@planetf1 planetf1 commented Jul 1, 2022 •
edited
Loading

…were skipped (gradle)

Signed-off-by: Nigel Jones [email protected]

Description

  • Uses traditional scanning for classes when using testNG with gradle (ie look for files, rather than scan classpath)
  • moves to same approach that was used for maven, to get to equivilance
  • some testNG tests were not running - as found in Open Connector Framework testng throwing output exceptions #6692
  • JUnit tests defaulted to a different scanner - and were working

Related Issue(s)

See #3370 for ongoing gradle build work

Testing

Release Notes & Documentation

Additional notes

@planetf1
odpi#3370 Use traditional class pattern scanning for testNG - some te…
acf6fa8 
…sts were skipped (gradle)

Signed-off-by: Nigel Jones <[email protected]>
@planetf1 planetf1 merged commit 6be0781 into odpi:master Jul 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@planetf1