-
Notifications
You must be signed in to change notification settings - Fork 624
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 JUnit 4 again #1104
Comments
Yep. It wasn't removed in a release though was it ?
…On Thu, 28 Nov 2019 at 20:53, Leonardo Colman Lopes < ***@***.***> wrote:
Removing support from JUnit 4 was a mistake.
Android UI tests cannot run without JUnit 4.
Perhaps it's better to implement a Android-runner than the JUnit4 runner?
(Although they'll be the same?)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1104>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFVSGWABTBUFSUSSVJVVB3QWB7ZTANCNFSM4JS2ITVQ>
.
|
No, snapshots only
On Fri., Nov. 29, 2019, 01:23 Stephen Samuel, <notifications@github.com>
wrote:
… Yep. It wasn't removed in a release though was it ?
On Thu, 28 Nov 2019 at 20:53, Leonardo Colman Lopes <
***@***.***> wrote:
> Removing support from JUnit 4 was a mistake.
>
> Android UI tests cannot run without JUnit 4.
>
> Perhaps it's better to implement a Android-runner than the JUnit4 runner?
> (Although they'll be the same?)
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#1104
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAFVSGWABTBUFSUSSVJVVB3QWB7ZTANCNFSM4JS2ITVQ
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1104>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMBCIYDQWZWWM5ASUTCXMLQWCKKXANCNFSM4JS2ITVQ>
.
|
Do android test still need junit4 with the recent work you've done ? |
Actually, let me see if there's a way to write tests without big workarounds using JUnit 5. |
But is the issue that things like roboelectric don't work with junit5
rather than android itself.
…On Mon, 13 Jan 2020 at 10:10, Leonardo Colman Lopes < ***@***.***> wrote:
Actually, let me see if there's a way to write tests without big
workarounds using JUnit 5.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1104>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFVSGWQVNUBX4WVGGLAHCDQ5SG7ZANCNFSM4JS2ITVQ>
.
|
No, android itself doesn't work with JUnit5 out-of-the-box, for UI tests |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm wanting to use Kotest, but I'm targeting Android, and as far as I know JUnit 5 is not really supported for Android development. Is it possible for me to use Kotest? If so, how? As far as I can see, JUnit 4 support has gone completely. |
Removing support from JUnit 4 was a mistake.
Android UI tests cannot run without JUnit 4.
Perhaps it's better to implement a Android-runner than the JUnit4 runner? (Although they'll be the same?)
The text was updated successfully, but these errors were encountered: