-
Notifications
You must be signed in to change notification settings - Fork 641
-
Notifications
You must be signed in to change notification settings - Fork 641
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
Focus not working in FunSpecs #1376
Comments
What is the expected behavior in this case. You're focusing the only test, so it should run? |
The example was not explicit enough perhaps so let me try again. Ideally I'd be able to focus on a single test but I was under the impression this is supported: internal class SomeTest : FunSpec() {
init {
context("f:my test 1") {
test("something 1") { ... }
test("something 2") { ... }
}
context("my test 2") {
test("blabla") { ... }
test("lala") { ... }
}
}
} I'd expect |
Yes that should work. I'll add your test and see.
…On Sat, 11 Apr 2020 at 13:42, Pin-Sho Feng ***@***.***> wrote:
The example was not explicit enough perhaps so let me try again. Ideally
I'd be able to focus on a single test but I was under the impression this
is supported:
internal class SomeTest : FunSpec() {
init {
context("f:my test 1") {
test("something 1") { ... }
test("something 2") { ... }
}
context("my test 2") {
test("blabla") { ... }
test("lala") { ... }
}
}
}
I'd expect something 1 and something 2 to be executed, as the top-level f:my
test 1 is focused.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1376 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFVSGRUD4L43ZTA3IWU3MLRMC2Y3ANCNFSM4MGDBRPA>
.
|
I've added test and they pass. Are you on 4.0.2 ? |
Thanks for this bug report. It is now fixed in master and will be included in 4.0.5. |
This is not working for FunSpecs:
According to the documentation, wouldn't
context
be considered a top-level scope and thus should work? Or is this a special case?The text was updated successfully, but these errors were encountered: