Feature/issue 11 Start of pytest testing

[frank113]

Summary

This PR provides a starting point to fully address issue #11 . More specifically some of the operations in patterns.py are tested using property-based testing. This PR is intended to be a first step in fully testing this package and provide velocity by accounting for house-keeping items (such as the dev installation type).

Issues Addressed

• 11

Changes made

1. Create a dev installation type in setup.cfg so that development dependencies can be installed as follows:

pip install -e .[dev]

2. Construct dev package list from an examination of workflows and libraries needed for testing, namely pytest and hypothesis
3. Add pytest configuration within setup.cfg
4. Add default hypothesis profile in tests/conftest.py
5. Create place for common strategy functions in tests/strategies.py
6. Add unit tests for the following functionality:
   • Set
   • Or
   • Amount (Limited and not property-based at this time)
   • join
   • Range
7. Add a main workflow to run unit tests either on command or within a PR
8. Update styling workflow to allow calling by workflow dispatch
9. Include changes from #14 so that all checks pass

Considerations

• The builders for all patterns tests generate a string. In a future release we can broaden the scope of these tests to generate a ValidPatternType
• The main.yml workflow refers to the version of styling.yml within the repository at the time of commit. In the future this will be updated to reflect the master state after styling.yml is merged into master

Other

While the process of unit testing everything in the package will be a long process I hope this PR provides velocity to kick off the process!

[frank113]

This PR refers to an outdated branch on my fork. Will close and open a fresh PR with the correct branch.