Add basic unit tests (try tinytest?)

[PMassicotte]

• Try the tinytest package cc @eddelbuettel (will need some help to configure Travis).

[eddelbuettel]

Sure. Now ... what would we test? The data does not stay the same...

[PMassicotte]

Very simple stuff:
1 - Returned df's are not empty
2 - Non-ascii keywords are not changed (encoding issues)

I just created a branch for it.

[eddelbuettel]

Ok. The .travis.yml should be straightforward for Linux as we get our for depends pre-built. (I do use a format that works well for me, but that not everybody else uses. Don't mean to impose it; happy to help with it. I can be extended to test on macOS too but I usually do not bother and just stick to Linux.)

Simple tests like that should be simple indeed.

[PMassicotte]

Should good to me :) Just exploring the package now, looks good!

[PMassicotte]

I have added few tests, feel free to add .travis.yml. Thanks in advance.

[eddelbuettel]

Looks complete, just append r-cran-tinytest to line 14 in .travis.yml so that tinytest is present. It is in the Rutter PPAs we use.

[eddelbuettel]

Yay!! (And that last step is the main annoyance with the simpler-yet-more-predictable approach I use -- it does not "learn" from DESCRIPTION so when you change Imports: or Suggests: you must change .travis.yml as well. Have forgotten it a dozen times myself ...)

[PMassicotte]

That makes sense, I will try to remember :)