Future request: Multi-threaded tests should be explicit about busted HOT 7 CLOSED

as mentioned in issue 24, I think that multithreading can be done at the testfile level. That would also be a perfect border for your case of depending tests. Or, also mentioned, at the top-level 'describe' functions, but in that case some documentation on this subject would be required.

from busted.

Yeah; I think we've decided that the threading will be per-file, with a flag to disable threads.

from busted.

as a request; check on Lanes being installed first, if not run sequential, otherwise use Lanes (unless flagged not to)

from busted.

I agree with the check idea. We should thread by default if lanes is installed, with an option to disable threading. If your tests break when threaded you're doing them wrong and deserve to have to do extra work to run your tests slower =)

from busted.

I vehemently disagree with a separate syntax for threaded tests. It clutters things.

from busted.

if you spawn threads on the file level, then I don't see why it would be necessary at all to have a separate syntax. Keep shared state at the file level and document the approach to multithreading. Syntax can stay as is.

from busted.

Hello Mr. DorianGray

I want to know when to perform multithreaded testing? can you please shed some insight on the same?

from busted.