Thanks to visit codestin.com
Credit goes to github.com

Skip to content

UTPLSQL Framwork: Though coverage is displayed in Sonar, unit test numbers are not showing up #1141

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
Closed
sv00362258 opened this issue Jun 3, 2021 · 4 comments
Closed

UTPLSQL Framwork: Though coverage is displayed in Sonar, unit test numbers are not showing up #1141

sv00362258 opened this issue Jun 3, 2021 · 4 comments
Labels
question

Comments

@sv00362258
Copy link

UTPLSQL Framwork: Though coverage is displayed in Sonar, unit test numbers are not showing up. So enabled debug mode in Sonarqube and did build, it is specifying 'Java CODE Block Indexer' skipped because there is no related file in current project' . I checked UTs and everything is written as mentioned in UTPLSQL document. Any help here would be appreciated
@lwasylow
Copy link
Member

lwasylow commented Feb 8, 2022

Can you provide a more information ?
A test used , command executed as well as share sonar properties file and sonar analysis output.

Cheers
Lukasz

@jgebal
Copy link
Member

jgebal commented Feb 10, 2022

Sonar stopped reporting unit tests (counts and details) from some version of sonar server.
We cannot see tests in our own utplsql sonar project too.
This is Sonar decisions. Not sure what was the rationale for it.

@felipebz
Copy link
Contributor

Hi,

I found this issue by chance when I was writing a guide on how to import test and coverage data to SonarQube and I think I can take a look at this. I've just tested the import on my own SonarQube server and on SonarCloud and the unit test count is shown correctly. Apparently, nothing changed from the SonarQube side.

@felipebz felipebz mentioned this issue Mar 2, 2022
Closed
@lwasylow
Copy link
Member

lwasylow commented Mar 4, 2022

Closed via #1198

@lwasylow lwasylow closed this as completed Mar 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@felipebz @jgebal @lwasylow @sv00362258