Tests: CI

[Andy Nowacki]

I very strongly urge you to consider setting up automated CI testing and code coverage reporting. This is strongly recommended by the JOSS reviewer guidelines.

If this is too expensive on Bitbucket, consider hosting the repo elsewhere, as CI is worth it and usually free elsewhere (e.g., Github or Gitlab).

‌

[Andy Nowacki]

I should clarify—CI isn’t absolutely required for publication in JOSS (just having tests) and if it is something you choose not to do in the end, that is fine for the purposes of the JOSS review. Just comment here or on the JOSS review issue on Github.

[Charlotte Haley]

This is a great suggestion. As of this commit, CI is implemented with Travis, while it also appears to be implementable using Bitbucket pipelines, though the latter seems to be currently incompatible with Coverage.jl.

[Andy Nowacki]

Fantastic!

Although I can see the Travis status badge on the README.md file, for some reason I can’t see the actual page that it links to. (I get a message saying “We couldn't display the repository
clhaley/multitaper.jl”.) Again, this isn’t critical for the review and I’m very happy to see this.

[Charlotte Haley]

Thanks for catching this, it looks like the URL https://travis-ci.com/clhaley/multitaper.jl needed to be changed to https://travis-ci.com/bitbucket/clhaley/multitaper.jl it works as of this commit.