Merged
Conversation
Member
Author
How to use the Graphite Merge QueueAdd 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. |
1d58640 to
4e7bc71
Compare
KaanOzkan
approved these changes
Aug 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Motivation
Closes #3561
It's not uncommon for Rubyists to have unit tests for some scripts that do not have any dependencies (no bundle). There were two issues preventing us from running tests:
Minitest::Test) and so the linearized ancestors the class only end up including itselfImplementation
For 1, I started checking if there's only the class itself in the list of ancestors, which indicates that we're hitting this scenario. In that case, I started including the parent class if available, which allows us to discover tests.
Note that there's one limitation: if the user introduces an intermediate parent class, we won't be able to discover the tests.
For 2, the method we should've been using is
with_unbundled_env, which removes Bundler related variables and allows us to discover if there's a main bundle in the project.Automated Tests
Added a test that reproduces.