Repository navigation
Allow developers to create Integration Tests without coding #78869
Copy link
Copy link
Closed
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projecta: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityc: proposalA detailed proposal for a change to FlutterA detailed proposal for a change to Fluttercustomer: crowdAffects or could affect many people, though not necessarily a specific customer.Affects or could affect many people, though not necessarily a specific customer.f: integration_testThe flutter/packages/integration_test pluginThe flutter/packages/integration_test pluginframeworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.team-frameworkOwned by Framework teamOwned by Framework teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-frameworkTriaged by Framework teamTriaged by Framework team
Description
It would be nice if developers could record their actions, and have that create an integration test that can later be automated.
Similar to: https://developer.android.com/studio/test/espresso-test-recorder.html
There are a few reasons this makes sense:
- According to twitter polls 60-70% of developers do not write any tests
- Writing tests is an entire sphere of knowledge, outside core Flutter development
I would picture it like this:
- Developer runs something like
flutter run --record-actions - They would use smoke test their app, pressing various btns
- Each action would be recorded as they proceed through the app
- After stopping the player, an integration test file is created
This would help many more devs use the integration testing abilities in Flutter, but also play well with some ongoing optimization tricks: #53609
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projecta: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityc: proposalA detailed proposal for a change to FlutterA detailed proposal for a change to Fluttercustomer: crowdAffects or could affect many people, though not necessarily a specific customer.Affects or could affect many people, though not necessarily a specific customer.f: integration_testThe flutter/packages/integration_test pluginThe flutter/packages/integration_test pluginframeworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.team-frameworkOwned by Framework teamOwned by Framework teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-frameworkTriaged by Framework teamTriaged by Framework team
Activity
zanderso commentedon Mar 24, 2021
Not sure if this is maintained: https://github.com/CareF/gesture_recorder
esDotDev commentedon Jan 8, 2022
This is another nice example of the same idea: https://developer.chrome.com/docs/devtools/recorder/
nilsreichardt commentedon Apr 23, 2022
@Norbert515 has built something like this with projecttest.dev 👍
jonahwilliams commentedon Aug 8, 2024
This is a cool idea but its not something the flutter team will take on
github-actions commentedon Aug 22, 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.