[Feature Request] Add pytest and emulation metadata testing

[terrancedejesus]

Overview

This PR adds pytest as a dependency to SWAT. It also adds test_emulation.py with several tests regarding emulation module metadata that is required. This emulation metadata is used to dynamically determine, scopes, services, ATT&CK mappings and more which affect other features.

Additional Information

• The pyproject.toml incorrectly pointed to README.md, this has been fixed.
• Added github workflow for pytest checks

Testing

• pytest addition: run pytest, pytest tests/ or poetry run pytest tests/
• emulations missing metadata: find an emulations and remove techniques, name, scopes, services or execute method and run tests

[Mikaayenson]

A couple small questions; otherwise LGTM

[Mikaayenson]

So every PR will have a change in the CHANGELOG? Might be good to unittest this.

[Mikaayenson]

nit: you could refactor all of these tests into a single test since you're using pytest and already using the parametrize decorator:

attributes_to_check = [
    ("parser", "has no parser defined"),
    ("services", "has no services defined"),
    ("scopes", "has no scopes defined"),
    ("techniques", "has no techniques defined"),
    ("execute", "has no execute method defined"),
]

@pytest.mark.parametrize("emulation", emulations_list, ids=lambda e: e.name)
@pytest.mark.parametrize("attribute,error_message", attributes_to_check)
def test_attributes_defined(emulation: Type[BaseEmulation], attribute: str, error_message: str):
    """Test if attributes/methods are defined in emulation."""
    assert hasattr(emulation, attribute), f'Emulation "{emulation.name}" {error_message}'

[brokensound77]

++

[brokensound77]

We should bucket the changelog under version bumps. Which means

• for changes requiring a version bump and targeting dev, they would bucket up
• for changes directly to main, they would append the current version