implement `pytest` testing

[jacobmartinez3d]

At this stage preparing full test coverage is not only necessary for deployment but is also going to help consolidate all the remaining todos and fixes left before initial alpha release.

[jacobmartinez3d]

1-implement-pytest-module

Figuring out how to handle dummy DB interactions with startup/teardown methods. Need to organize further into testsuites so I can loop over each entity-type while still having individual test-cases per-entity.

[jacobmartinez3d]

Noticing some really bad traceback barf when MaglaTest encounters bad seed data. Make sure to include good error handling for PR.

[jacobmartinez3d]

The test module will be merged in 3 stages:

Phase 1 (unit)

• test direct CRUD operations with SQLAlchemy session object.
• isolate and test individual sub-entities as far as possible without requiring other magla entities or modules(magla.utils is ok).
• make sure to always compare backend data with seed data used initially.

Methods available from within a sub-classed MaglaEntityTestFixture test:

# reset the seed object to match seed data
self.reset(seed_object)

# retrieve all seed data-tuples for given entity-type
self.get_seed_data("<entity name>")

# retrieve the seed data for a given entity and seed-index
self.get_seed_data("<entity name>", 1)

Phase 2 (critical integration)

• Complete the remaining test-coverage from phase 1 still using the same seed data from file.
• perform filesystem manipulation during this phase.

Phase 3 (expensive integration)

• Test all magla CRUD operations and remaining edge case tests.