Add unit tests and CI

[jardon]

This PR contains the following changes:

• Add pytest-based unit tests
• Add Github Actions CI for unit tests

Closes #72

[gerblesh]

Thanks for helping out with this. Not super familiar with pytest but the test code looks good to me so far!

[jardon]

@gerblesh @akdev1l do we actually want to add a test run to the spec file? I would think the unit tests would be run on PR in github actions CI

[gerblesh]

@gerblesh @akdev1l do we actually want to add a test run to the spec file? I would think the unit tests would be run on PR in github actions CI

If you had to ask me, I would say just github actions. Having it in the spec file would be redundant

[gerblesh]

I'm also planning on implementing some integration tests for the project soon as well so that'll probably be in the build/test action anyway, filling the role @akdev1l was mentioning

[gerblesh]

I like the idea of checking to see if the command has been ran properly, but this could also be a problem down the line if someone changes the arguments or if notify-send changes its cli. This also goes for a lot of these other subprocess calls. Testing subprocess is hard though and likely will need to be solved by integration tests down the line

[jardon]

ya its definitely tricky. the trap with unit tests at times is asserting too much as it makes the tests more inflexible and requires more maintenance on them. I could reduce the number of assertions to a more simple input -> output format that would allow changes to not break the tests as much.

[jardon]

but at the end of the day the unit tests are there to maintain stability of the codebase. changes to the unit tests are a often occurrence in my experience

[gerblesh]

This looks good to me then! Subprocess is a tricky one but after mulling it over it's probably better than not to at least test the arguments being passed in. Thanks so much for the great work here!