Repository navigation
Support flutter test on windows #8516
Description
flutter test should be supported on Windows; it's our core tool for unit testing.
This requires porting sky_shell to Windows.
{{ message }}
flutter test should be supported on Windows; it's our core tool for unit testing.
This requires porting sky_shell to Windows.
Activity
simonegiacomelli commentedon May 7, 2017
Just bumped into this... It would be useful to me.
mit-mit commentedon Jun 6, 2017
To "cast a vote" for this, please hit "thumbs up" on the top-most comment (the one by goderbauer) of this bug.
eseidelGoogle commentedon Jun 27, 2017
@bkonyi expressed some interest in looking at this.
mit-mit commentedon Jun 28, 2017
@bkonyi great to hear! cc @devoncarew
ride4sun commentedon Jul 18, 2017
@bkonyi @eseidel Any update when this will be available? I really think this should be available on Windows. Is there a workaround besides going to Linux.
bkonyi commentedon Jul 18, 2017
@ride4sun I'm currently working on this, but I'm not sure how long it will take to get done so I don't want to make any promises as to when it will be available. However, I am making good progress and will post updates when I have something to share, hopefully in the next week or two.
4 remaining items
Hixie commentedon Aug 17, 2017
We hope to have this done in less than a year, but probably more than weeks.
Hixie commentedon Aug 17, 2017
(Having said that, that's just a guess. See https://en.wikipedia.org/wiki/Forward-looking_statement for why we can't really give more specific estimates.)
JFixby commentedon Aug 31, 2017
anaisbetts commentedon Oct 4, 2017
A short-term workaround for this issue might be to do enough hax to get Flutter working under Windows Subsystem for Linux (aka "Bash for Windows"), this might be as simple as a few script fixups - as it stands, the initial run of
flutter doctorseems to hang on "Building Flutter tool..." (pub.dart.snapshot upgrade).Hixie commentedon Oct 5, 2017
On Windows, use the Powershell script rather than the bash script to bootstrap the flutter tool.
That's orthogonal to this issue, though, which is that we haven't ported the (C++) headless engine to Windows.
anaisbetts commentedon Oct 6, 2017
@Hixie I think you misunderstand - WSL is a full Linux environment on Windows, it natively runs ELF executables (i.e. if you build a Debian package in WSL, you can copy it byte-for-byte to a Linux box and it runs). You would not need to port the headless engine to Windows, you would run the Linux engine, possibly under something like
xvfb-run, which also executes on WSL.Hixie commentedon Oct 6, 2017
Ah, I see what you mean. Sure, that's one option. This bug is really about doing the actual port though.
Skylled commentedon Nov 17, 2017
Any updates on this? Most contributions require writing a test, and without the ability to run them on Windows I'm flying blind.
bkonyi commentedon Nov 17, 2017
@Skylled this is still a work in progress, but I've just recently gotten flutter_tester compiling and running on Windows. There's a bit of refactoring and cleanup work that still needs to be done, including some potential VM bugs that need to be fixed. I'm always hesitant to give timelines when I don't know the full scope of the bugs I'm seeing, but this issue should be resolved sooner than later.
bkonyi commentedon Nov 29, 2017
Quick update: I've started landing the changes needed to get flutter_tester working for Windows, but there are still some bugs that I need to investigate, so I won't be pushing all the changes to master just yet. If these aren't trivial bugs, I'll upload the changes with a temporary workaround on to a separate branch or put the binary somewhere for people who need this ASAP.
bkonyi commentedon Dec 11, 2017
As of PR #13459,
flutter testshould be functional on Windows. Checkoutmaster, delete%FLUTTER_PROJECT_LOCATION%\bin\cache\, and runflutter doctorto pull the new binaries to your machine.Run flutter test on appveyor (Windows)
github-actions commentedon Sep 4, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.