I think a good test for LuaConsole would be the total execution time based on multiple factors (calls to the program) outlined in the test from the travis.sh file.
It is based off of a target called, "Collect, Process, Output". The collection happens by the dll loader, which passes the data to the Processor and Output happens from there on. So I would also like test records of the collection process separately from total execution times.
Lua code execution time is irrelevant as it happens on part of the Lua library executing it, rather than the program interpreting it.
Finally, two sets of data would be nice. A debug and release form.
I think a good test for LuaConsole would be the total execution time based on multiple factors (calls to the program) outlined in the test from the travis.sh file.
It is based off of a target called, "Collect, Process, Output". The collection happens by the dll loader, which passes the data to the Processor and Output happens from there on. So I would also like test records of the collection process separately from total execution times.
Lua code execution time is irrelevant as it happens on part of the Lua library executing it, rather than the program interpreting it.
Finally, two sets of data would be nice. A debug and release form.