Document and test CouchDB module

[MatteoJoliveau]

Since we are approaching the first usable release we should start to pour more effort into documenting and cleaning up the codebase. One of the simplest modules to start is the CouchDB client.

TODO

• add integration tests for methods that interact with CouchDB. We can use the mockito library to mock the CouchDB API and provide assertions
• add documentation comments on every public type, function and method
• cleanup any Clippy warnings. This can be tested by running cargo clippy in the couchdb directory

[marcoieni]

I will work on this :)

[marcoieni]

Hi Matteo, I am really sorry but I didn't have a lot of fun while working on this, so at the moment I prefer to work on some other projects. Again, sorry! 😅

I removed the assignment in case someone else wants to work on this issue.

As a side note I leave you with a thought of mine: instead of mocking the CouchDB API wouldn't it be better to launch a local couchdb instance (for example with docker) and test the client against it?
I see two main benefits by doing so:

• enseada doesn't have to reproduce couchdb logic, so less code is required
• tests will be more reliable, since mocks could contain errors

[MatteoJoliveau]

No worries @marcoieni, totally understandable!

I personally prefere to have unit tests not depend on external network targets, but it's true that mocking is hard to do right. I'll consider your suggestion when I'll get around this task :)

[MatteoJoliveau]

I'm sorry you didn't have fun, is there something specifically that can be improved in order to make the codebase more pleasant to work with?

[marcoieni]

I think that for me the problem was adding tests and documentation to an already existing code base.
Maybe if I had to develop (and document and test of course) a new functionality it would have been better.
Anyway I will keep an eye on this nice project for the future :)