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
KotlinTest Roadmap 3.3 #628
Comments
I've like to release 3.3 as soon as possible because it's needed for the intellij plugin, which is by far the biggest feature. We can drop whatever we want to get it released. |
Ok, keep I'm ok to keep only some of the new matchers, and drop the uninmplemented ones and improvements to a future release. I don't see why we need to keep Not sure about retry helpers tho |
System properties are done, Environment is very close done and Security Manager will probably follow these 2 examples |
Ok I've bumped out those things. |
I think that with both Pull Requests being reviewed and approved, we're pretty much ready for this |
Ok I believe the plugin is just about good to go, with some bugs to fix. |
Can't we just go ahead and release what's on master? We're just missing documentation now |
Can do, just seeing if there's any low hanging fruit we can add in a day.
Also, I need you (if you have time) to test the plugin with the remaining
specs then at least we can say it's good enough for a first release.
Basically, I just want to make sure I don't have to change kotlintest much
if there's a bug in the plugin.
…On Wed, 13 Feb 2019 at 22:16, Leonardo Colman Lopes < ***@***.***> wrote:
Can't we just go ahead and release what's on master? We're just missing
documentation now
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#628 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAtZGr9vtyZa4g9FkAIfusRmCwnCEapJks5vNI6lgaJpZM4abANx>
.
|
I could sneak in #644 if you think it's a good feature while waiting on #184 to be tested. |
#644 is in |
Hey! I've been trying the new release to see if it's everything OK. Not sure if this has something to do with this release, but when using the 3.3.0-RC2 version, I get this error:
It doesn't happen when using the 3.2.1 It runs the tests anyway, it just appear as an initialization error, but it counts as a failed test: I've tried doing a mvn clean test, but it doesn't make any difference Let me know if you need more information |
Seems to be like the upgrade to JUnit Platform 1.4 has caused this. I guess they've compiled it with Java 11 and your runtime doesn't understand that. I think we should downgrade to 1.3 like before - I didn't realize JUnit 1.4 was using JDK11. @Kerooker thoughts? |
Actually I think it's because I have compiled this with JDK11. |
It seems it only affect Java files (which that one is).
|
Working perfectly now, thanks @sksamuel ! |
Great |
3.3.0 has been released. |
Features and fixes for 3.3
assertSoftly
Add project config option forassertSoftly
#512The text was updated successfully, but these errors were encountered: