-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[Test] Define broken
/skip
keyword argument for @test
#39322
Conversation
Side note, I feel like @test ... broken=true
@test ... skip=true but that ship has sailed already. Maybe good for v2.0? |
If we want that for 2.0, we should add the keyword version now so the ecosystem has plenty of time to transition. |
If there is consensus about adding |
stdlib/Test/src/Test.jl
Outdated
```jldoctest | ||
julia> @test_broken_if true 2 + 2 == 5 | ||
Test Broken | ||
Brokenped: 2 + 2 == 5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have absolutely no idea where this "Brokenped" was coming from 😳
@test_broken_if
and @test_skip_if
macrosbroken
/skip
keyword argument for @test
I've updated the pull request to define the |
Bump 🙂 |
Triage asks to add a NEWS.md item to show the |
Very nice feature!! |
I believe I addressed all comments from triage:
|
They make it less tedious having tests failing consistently only under specific conditions.
Bump 🙂 The failure on macOS is in Downloads, and looks unrelated (I think) |
Good to merge? 😃 |
…#39322) * [Test] Define `broken`/`skip` keyword argument for `@test` They make it less tedious having tests failing consistently only under specific conditions. * [Test] Use new `@test ... broken=cond` in some tests
…#39322) * [Test] Define `broken`/`skip` keyword argument for `@test` They make it less tedious having tests failing consistently only under specific conditions. * [Test] Use new `@test ... broken=cond` in some tests
…#39322) * [Test] Define `broken`/`skip` keyword argument for `@test` They make it less tedious having tests failing consistently only under specific conditions. * [Test] Use new `@test ... broken=cond` in some tests
They make it less tedious having tests failing consistently only under specific
conditions.