Skip to content
CodeQL

feat: check ability to detect abstractions and patterns in code INTELLIJ-29 #136

Sign in to view logs

feat: check ability to detect abstractions and patterns in code INTELLIJ-29

feat: check ability to detect abstractions and patterns in code INTELLIJ-29 #136

Triggered via pull request July 3, 2024 21:25
@kmruizkmruiz
opened #14
chore/intellij-29
Status Success
Total duration 6m 0s
Artifacts –

codeql.yml

on: pull_request
Matrix: analyze
Fit to window
Zoom out
Zoom in

Annotations

6 errors
NewConnectionActivatedProbeTestForAtlasCliEnvironment.should get proper build information of the server(Application, Project, MongoDbServerUrl): NewConnectionActivatedProbeTestForAtlasCliEnvironment#L1
Argument(s) are different! Wanted: telemetryService.sendEvent( <custom argument matcher> ); -> at com.mongodb.jbplugin.observability.TelemetryService.sendEvent(TelemetryService.kt:38) Actual invocations have different arguments: telemetryService.sendEvent( com.mongodb.jbplugin.observability.TelemetryEvent$NewConnection@74b97416 ); -> at com.mongodb.jbplugin.observability.probe.NewConnectionActivatedProbe.connected(NewConnectionActivatedProbe.kt:64)
NewConnectionActivatedProbeTestForLocalEnvironment.should get proper build information of the server(Application, Project, MongoDbServerUrl): NewConnectionActivatedProbeTestForLocalEnvironment#L1
Argument(s) are different! Wanted: telemetryService.sendEvent( <custom argument matcher> ); -> at com.mongodb.jbplugin.observability.TelemetryService.sendEvent(TelemetryService.kt:38) Actual invocations have different arguments: telemetryService.sendEvent( com.mongodb.jbplugin.observability.TelemetryEvent$NewConnection@63553e9f ); -> at com.mongodb.jbplugin.observability.probe.NewConnectionActivatedProbe.connected(NewConnectionActivatedProbe.kt:64)
DriverInFactoryMethodAbstractionTest.does detect a factory method for a collection(PsiFile): packages/mongodb-dialects/java-driver/src/test/kotlin/com/mongodb/jbplugin/dialects/javadriver/glossary/abstractions/DriverInFactoryMethodAbstractionTest.kt#L95
org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
DriverInFactoryMethodAbstractionTest.does detect a factory method in the same class(PsiFile): packages/mongodb-dialects/java-driver/src/test/kotlin/com/mongodb/jbplugin/dialects/javadriver/glossary/abstractions/DriverInFactoryMethodAbstractionTest.kt#L124
org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
DriverInFactoryMethodAbstractionTest.does detect a factory method for a client(PsiFile): packages/mongodb-dialects/java-driver/src/test/kotlin/com/mongodb/jbplugin/dialects/javadriver/glossary/abstractions/DriverInFactoryMethodAbstractionTest.kt#L37
org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
DriverInFactoryMethodAbstractionTest.does detect a factory method for a database(PsiFile): packages/mongodb-dialects/java-driver/src/test/kotlin/com/mongodb/jbplugin/dialects/javadriver/glossary/abstractions/DriverInFactoryMethodAbstractionTest.kt#L66
org.opentest4j.AssertionFailedError: expected: <true> but was: <false>