Weird behaviour with imported sequence tests

It seems like there’s something weird going on when a test is imported to be used in a plan of plans.

index.js

import zora from 'zora'
import example from './example.js'

zora()
.test(example)
.run()

example.js

import zora from 'zora'
export default zora({sequence: true})

.test('is run before', async assert => {
    await new Promise(resolve => setTimeout(() => resolve(), 1000))

    console.log('before')
    assert.ok(true, 'before')
})

.test('is run after', assert => {
    console.log('after')
    assert.ok(true, 'after')
})

Now, ‘after’ is logged at once, followed by ‘before’ after a second, if you run node -r @std/esm index.js.

If I append .run() and remove export default from example.js, and run it directly - it works! ‘before’ pops up first, followed by ‘after’.

Thought I’d let you know, even though the sequenced option is not yet documented 😃

[lorenzofox3]

No this is “normal” behaviour. For performance reasons tests are run in parallel (but reported in sequence). If you wish to respect the sequence you can pass the option {sequence:true} when you create your plan:

plan({sequence:true})
   .test('test1',async t=>{})
   .test('will not start before test 1 is done', t => {})

[oles]

Ahh, great to know. Currently rolling with just a simple import './tests/set.js' - works for now!