Added docstrings and 100% test and docstring coverage

[ohmycaptainnemo]

Hi @monim67,

I noticed that the tests only covered the code in the tests directory and there was no visibility on the source code coverage of the plugin code (code coverage was only 47% I think). I used poe poetry plugin like how you have done for linting and added a test-cov task for test coverage and a docstring-cov task for interrogating docstring coverage.
In the test-cov task, one has the option of publishing the coverage report either as xml which is good for uploading to a website like Codecov.io during the CI/CD actions and get a test coverage badge, or save the coverage report as html, for local viewing or download. I have left it as xml for now.

I changed the testing code to make sure while the tests in the tests directory run, the plugin source code also gets coverage. After getting visibility on the source code coverage, I noticed that everything is being covered by the tests except for a couple of minor if statements for the following cases:

1. The case in which the file with the version is not found.
2. The case in which the version was already what it needs to be and there is nothing to update.

I have added directories for those test cases.

Running the docstring coverage task currently will give you a .svg badge for docstring coverage too in the root directory.

Test coverage report in html:

Docstring coverage report:

I hope this helps. And also thank you very much for your hard work and contributions.

[monim67]

Poetry version should not change.

[ohmycaptainnemo]

I will change it back.

[monim67]

Is poetry.lock up to date now? Did you run poetry lock --no-update?

[ohmycaptainnemo]

Oh actually, I take it back. Do not merge.
For some reason I cannot get this to work with poetry 1.2.0a1. During the resolving dependency step, I just get an error like this:

I am not sure why it cannot set attribute. I need to look into this.
Also I was wondering, is there any reason why we cannot use poetry 1.2.1 ?

[monim67]

People using poetry 1.2.0a1 might also want to use this plugin.

[monim67]

Can you get it working with ^1.2.0a2? 1.2.0a1 might be broken.

[ohmycaptainnemo]

Ahh sorry. You make sense.
It is interesting that you should say that because I am having issues with 1.2.0a1.
I will try 1.2.0a2 and see how it goes.

[ohmycaptainnemo]

It is all working for poetry 1.2.0a2.
I have updated poetry.lock and pyproject.toml.