-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Add support for Kotlin Android plugin #33
Conversation
d74454e
to
087517e
Compare
@@ -65,8 +66,7 @@ class BurstGradlePluginTest { | |||
|
|||
val taskName = ":lib:$testTaskName" | |||
val result = createRunner(projectDir, "clean", taskName).build() | |||
assertThat(SUCCESS_OUTCOMES) | |||
.contains(result.task(taskName)!!.outcome) | |||
assertThat(result.task(taskName)!!.outcome).isIn(*SUCCESS_OUTCOMES) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -20,4 +23,15 @@ allprojects { | |||
mavenCentral() | |||
google() | |||
} | |||
|
|||
tasks.withType(JavaCompile::class.java).configureEach { | |||
sourceCompatibility = "1.8" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
None of these projects built on my machine without this. My default JDK is 23, but Kotlin doesn't know about that version so it drops down to target 22 and then complains Kotlin and Java targets don't match.
@Burst | ||
class CoffeeTest( | ||
private val espresso: Espresso, | ||
) { | ||
@BeforeTest | ||
fun setUp() { | ||
println("set up $espresso") | ||
} | ||
|
||
@Test | ||
fun test(dairy: Dairy) { | ||
println("running $espresso $dairy") | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are those tests just validating the compilation step ? I don't think we're reading the printed lines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. We'd need an emulator to run the instrumented tests and the JVM ones are identical to the existing JVM tests.
I can add it in a follow-up if we want them.
Closes #27