Auto resolve first test file of each top level directory

[vinistock]

Motivation

We identified a challenge when resolving test commands for entire test directories where not every file has been expanded. How do we know what add-on should resolve the command if we haven't discovered the examples inside?

For example, if an application has a spec directory, how do we know if we're dealing with RSpec or Minitest spec style? They require different commands to execute the tests inside the directory.

One possible solution would be to discover all tests inside the requested directory, but that would be very slow. A decent compromise proposed by @st0012 was to resolve only 1 test file inside a top level directory and then assume that all tests inside of it belong to the same framework. I think this is reasonable given that mixing test frameworks inside the same directory is not a very common usecase.

This PR starts auto resolving 1 of the test files discovered inside each top level test directory and then associates everything nested under that directory with the same framework tag, so that add-ons can resolve commands only for the items they are interested in.

Implementation

The idea is to keep track of the framework tag during test file discovery. Whenever we find a new top level test dir, we reset the tag to discover it again.

Then we resolve the specific test file, so that the server can return what framework that file is associated with, which we associate to all items under that directory.

Automated Tests

There were some duplicate examples in our tests and quite a bit of duplicate code. I cleaned them up a little bit and adjusted some expectations.

[vinistock]

• Auto resolve first test file of each top level directory #3349 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label graphite-merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.