traceback on error?

[JustAPerson]

Perhaps there could be a flag that enables printing the traceback upon a failed test that errors unexpectedly?

Right now I only get the single error line when something goes wrong in my code, but I think more context such as the traceback could be useful.

Failure → src/test.lua @ 35
LOADK - Boolean
./src/main.lua:71: attempt to perform arithmetic on local 'd' (a nil value)

Since this is inside of a function I use everywhere, I believe a little more context would help actually resolve it.

[Tieske]

have you tried the verbose option; -v ?

[DorianGray]

This brings up another issue. We should probably document the command line outside of the command line itself. Currently to learn about the command line you have to open up a command prompt and run busted --help

[Tieske]

it is in the docs; http://olivinelabs.com/busted/#usage

[DorianGray]

Ah, right, I searched the wrong place. Closing this then as OP + myself didn't read. =)