Testing and CI about dot HOT 9 OPEN

I'm thinking we should use buttercup for tests.

from dot.

Linting will be a combo of CEDET's checkdoc and elisp-lint.

from dot.

I'm doing research rn on the best approach for testing. We also should get linting set up and put both of those into CI. Suggestions on CI are welcome. I'll update this at some point soon with a roadmap for testing/linting.

from dot.

I'm gonna start work on this using these. lmk asap if you have an issue with that. planning on using travis

from dot.

I edited the initial comment to include a task list.

from dot.

I'm not sure about using Coveralls out of necessity. Do you know if CodeClimate supports EmacsLisp?

from dot.

I'm pretty sure it doesn't. I already have basic Coveralls support in the coverage-reporting branch. The overhead is pretty minimal. I'm not super satisfied with it at this point, which is why I haven't opened a PR, but at the same time, it's kinda a "why not" thing.

from dot.

Are we good with using undercover? Due to the way coverage libraries for emacs lisp are implemented, it will only show coverage for files that are at least a little tested... so the percentages may be off at first. Still should be a useful tool and I already pretty much have it implemented.

from dot.

I'm open to whatever you have, so long as it works.

from dot.