Why are coroutines used? about busted HOT 6 CLOSED

+1

a potential use could be async testing, but that would a whole different thing than the current use of coroutines. Busted does not have a scheduler to run the different coroutines, hence its sequential and hence slower (and in current code, as a side effect, it runs the wrong order).

from busted.

We need to add a mechanism for async testing, to handle things like testing web requests, database connections, etc for integration testing. We'll accomplish this separately from the threading issue, since this will be per-test rather than per-file. I assume we'll use coroutines for that.

from busted.

Coroutines were implemented as a placeholder for lualanes. I want each file to run in a separate thread eventually, for now I just broke it out at the describe block level. It forced me to decouple the test runner and make it async.

from busted.

It forced me to decouple the test runner and make it async.

Probably you didn't mean that exactly. In (vanilla) Lua you can't have async things. It's a sync language, coroutines included.

If coroutines they are an "experimental stand-in" for lualanes, I would recommend moving them to an "experimentation branch" - leave master as simple as possible (i.e. tables and functions) until the Lualanes implementation is ready.

In any case, the reason is explained, so I consider this issue closed.

from busted.

Probably you didn't mean that exactly. In (vanilla) Lua you can't have async things. It's a sync language, coroutines included.

If strictly sticking to unit tests, you're right. But there are many libraries that do async stuff, usually they are the ones implementing main-loops. Copas as a socket scheduler for example, or any app using QT. For those you might want an async test.

from busted.

Also, being able to have a maximum execution time on tests is nice, for performance testing. Threads give us that, and that's valuable for single threaded apps as well.

from busted.