Skip to content

"Run Tests" explorer option does not discover tests before trying to run #212342

Closed

Description

@DanTup

If I open a Dart project, right-click on a folder in the explorer and then "Run Tests", I see:

image

However if I open the test explorer tree first and then try again, everything works.

It appears that "Run Tests" from explorer does not trigger the resolveHandler to allow initial test discovery.

(Connor Peet (@connor4312) I presume this is a bug and not intended?)

Activity

  1. DanTup commented on May 9, 2024

    @DanTup
    ContributorAuthor

    Connor Peet (@connor4312) even after I've shown the explorer tree and triggered discovery, it seems like "Run Tests" now works on the "tests" folder, but not on an individual test file (even though I've confirmed the URI for that file is being set when creating the test tree item).

    Is there something else I need to do besides having the URI on the test file node?

  2. connor4312 commented on May 9, 2024

    @connor4312
    Member

    Does this reproduce on Insiders for you? It should be fixed with #211338

  3. DanTup commented on May 9, 2024

    @DanTup
    ContributorAuthor

    Connor Peet (@connor4312) looks like that fix handles the second issue above (running the file now works), however the original issue above is still an issue - if I don't trigger discovery of the tests before using it, it reports no tests found.

  4. added
    bugIssue identified by VS Code Team member as probable bug
    testingBuilt-in testing support
    and removed
    info-neededIssue requires more information from poster
    on May 9, 2024
  5. added a commit that references this issue on Jun 4, 2024
    578a1ce
  6. added a commit that references this issue on Jun 4, 2024
    447099b
  7. added
    insiders-releasedPatch has been released in VS Code Insiders
    and removed
    unreleasedPatch has not yet been released in VS Code Insiders
    on Jun 5, 2024
  8. DanTup commented on Jun 10, 2024

    @DanTup
    ContributorAuthor

    Fix works for me, thanks! :)

    /verified

  9. locked and limited conversation to collaborators on Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsiderstestingBuilt-in testing supportverifiedVerification succeeded

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions