OK, I can understand SL not running third-party tests and can live with that, although it would be nice if SL at least showed the results from the SQ server to help me address them in the Eclipse UI.
As to your other questions, all the issues I mentioned are with the same .java file, so both SL and SQ are scanning it. I’m not sure why SQ would classify it as test or how to confirm if that’s what’s happening. We’re running the SQ scanner in Jenkins and it appears to be version 3.2.0.1227.
I just tried enabling the verbose SL console logs and I don’t see anything concerning. I’ll paste the results after editing the file and saving it to trigger and SL scan:
Trigger: EDITOR_CHANGE
Clear markers on 0 excluded files
SonarLint processing file /zendesk-automation/src/main/java/com/copart/automation/zendesk/dao/ZDJpaDao.java...
Connected mode (using configuration of 'zendesk-automation' in server 'sonarqube.copart.com')
Starting analysis with configuration:
[
projectKey: zendesk-automation
baseDir: /Users/kcbaltz/git/zendesk-automation
workDir: /Users/kcbaltz/Documents/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/zendesk-automation/org.sonarlint.eclipse.core
extraProperties: {sonar.java.target=1.8, sonar.java.libraries=...
inputFiles: [
file:/Users/kcbaltz/git/zendesk-automation/src/main/java/com/copart/automation/zendesk/dao/ZDJpaDao.java (UTF-8)
]
]
Found 2 issue(s)
Done in 104 ms