Skip to content

Allow developers to create Integration Tests without coding #78869

Closed

Description

@esDotDev

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

Activity

  1. added
    in triagePresently being triaged by the triage team
    a: tests"flutter test", flutter_test, or one of our tests
    f: integration_testThe flutter/packages/integration_test plugin
    c: proposalA detailed proposal for a change to Flutter
    c: new featureNothing broken; request for a new capability
    and removed
    in triagePresently being triaged by the triage team
    on Mar 23, 2021
  2. zanderso commented on Mar 24, 2021

    @zanderso
    Member

    Not sure if this is maintained: https://github.com/CareF/gesture_recorder

  3. esDotDev commented on Jan 8, 2022

    @esDotDev
    Author

    This is another nice example of the same idea: https://developer.chrome.com/docs/devtools/recorder/

  4. added
    customer: crowdAffects or could affect many people, though not necessarily a specific customer.
    on Jan 31, 2022
  5. nilsreichardt commented on Apr 23, 2022

    @nilsreichardt
    Contributor

    @Norbert515 has built something like this with projecttest.dev 👍

  6. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    frameworkflutter/packages/flutter repository. See also f: labels.
    on Apr 26, 2022
  7. added
    P3Issues that are less important to the Flutter project
    and removed on Jun 28, 2023
  8. jonahwilliams commented on Aug 8, 2024

    @jonahwilliams
    Contributor

    This is a cool idea but its not something the flutter team will take on

  9. github-actions commented on Aug 22, 2024

    @github-actions

    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.

  10. locked as resolved and limited conversation to collaborators on Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projecta: tests"flutter test", flutter_test, or one of our testsc: new featureNothing broken; request for a new capabilityc: proposalA detailed proposal for a change to Fluttercustomer: crowdAffects or could affect many people, though not necessarily a specific customer.f: integration_testThe flutter/packages/integration_test pluginframeworkflutter/packages/flutter repository. See also f: labels.team-frameworkOwned by Framework teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-frameworkTriaged by Framework team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions