SUGGESTION: Coverage debug log

[SSH]

For people doing beta-testign of their game, it would be great if AGS had a debug mode which you could turn on that logged Statement coverage of your game to a file which each beta-tester could send to the developer, so a developer can know if every bit of code has been exercised. Ideally, also have decision coverage too, but that's probably harder...

[Rui 'Trovatore' Pires]

I know it's hardly the same thing, but AGS does have a "record" feature that's hardly ever used. I second SSH's suggestion, but I think that first AGS' "record" feature should be properly documented.

[SSH]

Well, I'm not sure it shoudl happen "first" as its probably not used because it is not useful. I'm trying to improve testing quality by providing metrics with this suggestion...

[Pumaman]

Recording code coverage would probably require fairly significant changes to the script engine, but it's certainly an interesting suggestion for the long-term.

[SSH]

Well, of course the easy way would be to make every line effectively annotated to have some code like Covered(LINE_NO, SCRIPT_NAME); if front of it... which if the new editor uses plain files for script would just require some kind of pre-compile preprocessing hook in the editor.

[Pumaman]

Yes, but you then also need a way to present the results such that it's easy to see which lines were covered and which weren't...

[SSH]

Well, that could be done externally by anyone who likes to create AGS add-ons