Automated tests are needed

It would be great to have automated smoke tests to check that most important functionality is not broken after changes.

If not possible, at least manual instructions what to check and how.

[Hackerpilot]

It's something I've been meaning to work on. The previous version of this program (https://bitbucket.org/SirAlaran/dscanner/overview) had much better unit test coverage. I'll be adding unit tests gradually over the next few days.

If by unit testing you mean checking parts of system, it would be also great to have some script running dscanner executable several times with different options and checking that basic functionality is not broken (smoke test).

[Hackerpilot]

I currently do not have plans to do this because I've already integrated dscanner into my editor. If something breaks, I will know almost immediately. I do plan on adding more unit tests to the tokenizer/lexer though. If you write smoke tests I will likely pull them in.

Ok, that's fine.