Apply correct hierarchy and IDs to Minitest spec items

[vinistock]

Motivation

We were incorrectly creating the test hierarchy for Minitest specs. First, we weren't handling the nesting correctly for classes.

Second, we were not properly matching what Minitest does if you decide to create a test group using a class inside a describe. In this scenario, Minitest does not use the describe's description as part of the resulting group ID. For example:

class MySpec < Minitest::Spec
  describe "something" do
    class InnerSpec < Minitest::Spec
      it "works" do
      end
    end
  end
end

The correct ID for the inner spec group is MySpec::InnerSpec and not MySpec::something::InnerSpec.

Implementation

I started using a flat stack of group IDs that differentiate between a class group or a describe group, so that we can do the right thing depending on what we find.

Automated Tests

Added tests.

[vinistock]

• Apply correct hierarchy and IDs to Minitest spec items #3501 👈 (View in Graphite)
• Add spec to load path when running Minitest specs #3500
• 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.