Test suite cannot run with documented defaults

[miciav]

Description

Running pytest fails before collection because required third-party dependencies (requests, responses, typer, fastapi, etc.) are missing and the maestro package itself is not importable until it is installed.

Location

• pyproject.toml (L26-L62)
• Test setup documentation

Impact

• New contributors cannot run tests
• CI/CD may fail if setup is not explicit
• Development workflow is hindered

Expected Fix

1. Update setup/installation documentation to include test dependencies
2. Add clear instructions to install with: pip install -e .[test] or uv pip install -e .[test]
3. Consider adding a development setup script
4. Update CI configuration to ensure proper installation

[DavideCorigliano-Unimib]

I'll take charge of this issue. I'll work on it and let you know as soon as possible.

[DavideCorigliano-Unimib]

After working on this issue, I can confirm that the test suite now starts successfully using the documented defaults.

By setting up the project environment through uv (which automatically installs and manages all required dependencies), the test suite can be executed correctly via:

uv run pytest

I’ve also added a note in the README.md file to remind contributors to use uv run before running any command, since uv ensures that every required dependency is properly available in the environment.

---

I’ve submitted a pull request that states that the issue has been fixed.