Open jezzsantos opened 1 month ago
Thx @AlexanderBartash Sorry, it's not obvious to me where to look. Can you direct me? (I am on Windows)
just for the record my test task list declared like this, which I am not confident is correct for version 2.0 of the intellij plugin
tasks {
wrapper {
gradleVersion = "${gradleVersion}"
}
publishPlugin {
token.set(System.getenv("ORG_GRADLE_PROJECT_intellijPublishToken"))
channels.set(List.of(("${thisPluginVersion}".split("-").length > 1) ? "${thisPluginVersion}".split("-")[1] : "default"))
var versionExists = changelog.has("${thisPluginVersion}")
if (versionExists) {
patchPluginXml.changeNotes.set(changelog.renderItem(
changelog
.get("${thisPluginVersion}")
.withHeader(false)
.withEmptySections(false),
Changelog.OutputType.HTML
))
}
}
patchPluginXml {
changeNotes.set(changelog.renderItem(
changelog
.getUnreleased()
.withHeader(false)
.withEmptySections(false),
Changelog.OutputType.HTML
))
}
test {
systemProperty "LOCAL_ENV_RUN", "true" //For use with 'BaseTestWithSolution' and TestNG
useJUnitPlatform()
minHeapSize = "512m"
maxHeapSize = "1024m"
testLogging {
showStandardStreams = true
exceptionFormat = TestExceptionFormat.FULL
}
}
runIde {
autoReload = false
maxHeapSize = "2G"
}
}
full code can be found here: https://github.com/jezzsantos/automate.plugin-rider/blob/main/build.gradle
@jezzsantos See https://plugins.jetbrains.com/docs/intellij/tools-intellij-platform-gradle-plugin-types.html#TestFrameworkType
Using Bundled
The Bundled type should not be used unless it is necessary, like in the case of [Rider](https://plugins.jetbrains.com/docs/intellij/rider.html), as its test-framework is not published as an artifact.
Btw, not sure if you saw this https://github.com/JetBrains/intellij-platform-plugin-template may be useful.
I guess this plugin still could log a warning or something, would save you time.
Thanks @AlexanderBartash
Sorry, none of what you have given here has helped.
I believe I should be using testFramework TestFrameworkType.Bundled.INSTANCE
since this is a Rider plugin, unless I am mistaken.?
Do you think I have structured the test
task properly for version 2.10. of the plugin? here in: https://github.com/jezzsantos/automate.plugin-rider/blob/main/build.gradle
@jezzsantos According to this documentation https://github.com/JetBrains/intellij-platform-gradle-plugin/issues/1793#issuecomment-2409476513 the missing jar is expected behavior. I have never tried to create any plugins for Rider, but if that is so, most likely you should try to use testFramework(TestFrameworkType.Platform)
or other option.
It turned out that Rider doesn't distribute the testFramework.jar
with the Rider installers. Investigating.
What happened?
Since upgrading from 1.16.1 to 2.1.0, and upgrading to
2024.1
of Rider, I am unable to compile and run my tests.I am unable to
import com.jetbrains.rider.test.base.BaseTestWithSolution;
and use theBaseTestWithSolution
type.I know a bunch has changed with this new version, becuase this type used to exist in the
testFramework,jar
incom.jetbrains:riderRD:2023.3
That jar file is no longer loaded by gradle for some reason. I have done what I see mentioned in the docs to my gradle file, but I have had no luck importing that type.
Here is the top of my
build.gradle
(groovy) file:Relevant log output or stack trace
No response
Steps to reproduce
Rider plugin Upgrade intellijplugin from 1.16.1 to 2.1.0 Upgrade Gradle from 8.5 to 8.10.2 Upgrade platformVersion from 2023.3 to 2024.1
Gradle IntelliJ Plugin version
2.1.0
Gradle version
8.10.2
Operating System
Windows
Link to build, i.e. failing GitHub Action job
No response