Skip to content

Debugging tests is unnecessarily hard #163

Closed

Description

@FlutterIssues

Issue by Hixie
Wednesday Sep 16, 2015 at 19:49 GMT
Originally opened as https://github.com/flutter/engine/issues/1196


It would be great if there was a way to launch a single test in Observatory. Right now since there's no way to set breakpoints before you've loaded the code, the only way I can think to do it is to modify the code to call debugger(), then run the test, then attach the debugger (somewhere? it's not clear where to attach it, really). Really I want the equivalent of "start with gdb" but for observatory.

Activity

  1. added
    a: tests"flutter test", flutter_test, or one of our tests
    on Nov 9, 2015
  2. FlutterIssues commented on Nov 9, 2015

    @FlutterIssues
    Author

    Comment by sethladd
    Friday Sep 18, 2015 at 01:48 GMT


    cc @devoncarew as we're exploring a debugger

    Would make a ton of sense to right-click on a single test and run that, with the debugger, from Atom

  3. modified the milestone: on Dec 12, 2015
  4. modified the milestone: on Feb 3, 2016
  5. eseidelGoogle commented on May 13, 2016

    @eseidelGoogle
    Contributor

    @Hixie has a patch in progress which may address some of this?

  6. Hixie commented on May 13, 2016

    @Hixie
    Contributor

    It's not yet easy to debug a test under flutter test in observatory. What I'm doing will make it possible to test under flutter run, but that's not really the same.

  7. sethladd commented on Sep 20, 2016

    @sethladd
    Contributor

    Did we make progress on this?

    I'd like to clarify this request is for making it easier to debug a test without using an IDE. We could open a separate request for a test runner (implied: debugging) in the IDE plugin, but I believe you are looking for a solution without the IDE?

  8. added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 20, 2016
  9. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    and removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Dec 9, 2016
  10. Hixie commented on Dec 9, 2016

    @Hixie
    Contributor

    What we need to resolve this is support for flutter test --start-paused filename.dart.

  11. self-assigned this
    on Jan 23, 2017
  12. added a commit that references this issue on Jan 23, 2017
  13. github-actions commented on Aug 8, 2021

    @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.

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

Metadata

Metadata

Assignees

Labels

a: tests"flutter test", flutter_test, or one of our testsc: new featureNothing broken; request for a new capabilitytoolAffects the "flutter" command-line tool. See also t: labels.waiting for PR to land (fixed)A fix is in flight

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions