benkuly
05/03/2022, 12:14 PMsam
05/03/2022, 1:21 PMsam
05/03/2022, 1:22 PMbenkuly
05/03/2022, 1:26 PMrunTest
seems to have promise on method level. Could that be used by kotest as a workaround? Otherwise as far as I understand, I need to make my test not nested and then I could just switch to kotlin.test, because I use kotest-framework mainly because of nested tests^^sam
05/03/2022, 1:27 PMbenkuly
05/03/2022, 4:05 PMrunBlocking
and spawn the needed coroutines?sam
05/03/2022, 4:06 PMtest("foo") {
test("bar") {
test("baz") {
}
}
}
Where each block is it's own coroutine, and the underlying JS frameworks only support promises at the outer most layerbenkuly
05/03/2022, 4:10 PMsam
05/03/2022, 4:11 PMsam
05/03/2022, 4:11 PMbenkuly
05/03/2022, 4:34 PMit
block. So maybe just something like this? This could be totaly wrong, but I want to understand, why this is not possible.
it("TestBlock"){
runTest {
}
}
sam
05/03/2022, 4:34 PMit
blocksam
05/03/2022, 4:34 PMit
but the parent parts must map to the describe
bit, and describe != promises in JS landsam
05/03/2022, 4:35 PMcontext("foo") {
test("bar") {
}
}
Both of those are async in Kotest ^^
describe("foo") { <--- sync
it("bar") { <--- promise
}
}
In JS Land ^^sam
05/03/2022, 4:35 PMbenkuly
05/03/2022, 4:40 PMit
level and run multiple tests within the it
block? I know this would prevent running all tests, when on of them fails, but it would allow nested tests
context("foo") {
test("bar") {}
test("baz") {}
}
to
it("foo") {
test("bar") {}
test("baz") {}
}
sam
05/03/2022, 4:41 PMsam
05/03/2022, 4:42 PMbenkuly
05/03/2022, 4:43 PMsam
05/03/2022, 4:43 PMbenkuly
05/04/2022, 9:22 AMbenkuly
05/04/2022, 10:09 AMsam
05/04/2022, 10:25 PMbenkuly
05/05/2022, 1:34 PMbeforeSpec
and afterSpec
seems to get ignored.
• The fail output doesn't make clear, which subtest has failed.
Maybe you have ideas to fix these issues, because I just don't understand, where to start 😄sam
05/05/2022, 1:35 PMbenkuly
05/05/2022, 1:38 PMsam
05/05/2022, 1:38 PMbenkuly
05/05/2022, 5:23 PM