You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Provide option for Flutter driver to create machine-readable output #51135
This came up in a chat with @helinanever and @martinjeret at Nevercode, who indicated that this would be useful for some of their clients in building E2E CI/CD/test solutions.
Currently flutter drive does not use the reporting mechanism from package:test, and the host script is executed just like any other dart script. This also means that -rexpanded argument that is passed by default doesn't do anything.
I put together #73017 as a quick hack to show the pieces that are needed for this.
This is something that I would like to work on.
Is adding a flutter drive --reporter=json reasonable? Assuming this would work by relaying the flag to test
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 -v and a minimal reproduction of the issue.
Activity
jmagman commentedon Feb 20, 2020
Subset of #14134.
jmagman commentedon Feb 20, 2020
See also #50449.
NanYeYe commentedon Mar 30, 2020
@kf6gpe @jmagman
Is here have solution now?
dnfield commentedon May 13, 2020
This may not be necessary if you can use package:e2e instead.
ened commentedon Dec 22, 2020
@dnfield Is this functionality (machine readable output) already available in e2e (integration_test) packages? I can not find it, yet.
dnfield commentedon Dec 24, 2020
No, but it should be possible.
I'm actually not sure why the machine reporter can't be used with package:flutter_driver though. /cc @jiahaog who might know
jiahaog commentedon Dec 28, 2020
Currently
flutter drivedoes not use the reporting mechanism frompackage:test, and the host script is executed just like any other dart script. This also means that-rexpandedargument that is passed by default doesn't do anything.I put together #73017 as a quick hack to show the pieces that are needed for this.
Then something like
Could work, or we could provide something like
--machinetoflutter driveto avoid leaking the package:test abstractionrrousselGit commentedon Oct 10, 2021
Hello!
This is something that I would like to work on.
Is adding a
flutter drive --reporter=jsonreasonable? Assuming this would work by relaying the flag totestDanTup commentedon Oct 11, 2021
@rrousselGit I don't know if it covers everything, but you can write integration tests to work with the
flutter testcommand now (see https://flutter.dev/docs/testing/integration-tests#running-using-the-flutter-command). This works with the JSON reporter and is what VS Code now uses so you can have integration tests in the test runner tree.cheuk0324 commentedon Feb 21, 2024
matanlurey commentedon Jul 26, 2024
It turns out this feature accidentally is supported, so I am going to document it.
Making this more first-class (and the default) is more work that I'll track elsewhere:
#152409
Document that `flutter drive --test-arguments` can opt-in to `dart te…
Document that `flutter drive --test-arguments` can opt-in to `dart te…
github-actions commentedon Aug 10, 2024
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.Document that `flutter drive --test-arguments` can opt-in to `dart te…