-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use ancestors to determine test framework in code lens #1334
Labels
enhancement
New feature or request
pinned
This issue or pull request is pinned and won't be marked as stale
rubyconf-hackday
Comments
That would be great. |
1 task
This issue is being marked as stale because there was no activity in the last 2 months |
vinistock
added
pinned
This issue or pull request is pinned and won't be marked as stale
and removed
Stale
labels
Apr 1, 2024
5 tasks
This was referenced Jun 12, 2024
As a note, when we implement this, we should look for That would let us support users who want to support the declarative syntax of AS::TC, who don't wish to use the whole thing. |
+1 This would be a great feature! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
pinned
This issue or pull request is pinned and won't be marked as stale
rubyconf-hackday
Depends on #1333
We currently try to determine the test framework based on dependencies. This is an okay approach, but once we have ancestors available we can be a lot more accurate.
We can check if a test inherits from
Minitest::Test
orTest::Unit::TestCase
and then decide based on that - ideally with a fallback if we can't determine the framework for whatever reason.The text was updated successfully, but these errors were encountered: