Add more test coverage, implement integration testing

[Diapolo10]

At present, the critical parts of the library have decent unit test coverage (not that it shows because Coveralls integration is still missing), but more should be added. Furthermore the library could use some integration testing.

[ben-hill33]

Good afternoon! You mind if I contribute to this?

[Diapolo10]

Good afternoon! You mind if I contribute to this?

Sure, go right on ahead!

[ben-hill33]

Thanks! So I was a little confused on what needed to be covered so I just looked at the the top of the test file to see what methods were being imported that wasn't used yet, compared the function being tested to what it was checking for from the original file, and just ran a few assertions.
It was my first time make a real contribution to a project, so thank you for the opportunity and I apologize if I wasn't really any help!

[Diapolo10]

That confusion is entirely my fault, I haven't had time to write proper documentation or detailed issues yet as for the last few months I've been razor-focused on an issue with the CI/CD build system, which I finally managed to fix today (for now).

I'm not fussy about what assertions people add, everything helps as long as it's not just duplicating existing cases.

I'll be sure to read through your pull request and approve it unless there's something really weird going on, and thank you for your time! Feel free to contribute in other ways if you see something that interests you.