Feature/cli refactor tests

[dschwartznyc]

CLI Refactoring and Test Suite Reorganization

Summary

This release introduces a significant refactoring of the PythonCodeGeneratorCLI and a major reorganization of the Python unit test suite. The primary goals are to improve the robustness of the command-line interface, enhance validation feedback, and restructure the testing framework to be more maintainable and aligned with the current capabilities of the generator.

Key Changes

1. CLI Refactoring and Enhancement (PythonCodeGeneratorCLI.java)

The CLI has been updated to "v2" with several improvements:

• Robust Validation: Integrated IResourceValidator to perform full model validation before code generation. The tool now identifies and logs specific validation errors (including line numbers and element context) and skips invalid models.
• Target Directory Management: Added logic to safely clean and recreate the target directory before generation, preventing "stale" code from persisting.
• Improved Logging: Migrated to SLF4J for consistent logging and provided clearer console output for progress and errors.
• see issue #142

2. Test Suite Reorganization (test/python_unit_tests/)

The Python test suite has been restructured from a flat or ad-hoc layout into a categorized hierarchy:

• Feature-Based Categorization: Tests are now organized into logical folders:
  • features/model_structure/: Tests for inheritance, entity reuse, metadata, etc.
  • features/operators/: Tests for arithmetic, comparison, and boolean logic.
  • features/robustness/: Tests for null handling and edge cases.
• Integrated Rosetta Sources: Rosetta files used for tests are now co-located with their corresponding Python tests within the features/ directory tree, making it easier to understand the relationship between the DSL source and the test assertions.

3. "No-Function" Test Alignment

In alignment with the current generator status (where full function generation is still in progress), many tests were refactored to verify logic using Type Conditions rather than standalone Functions.

• Rationale: This allows for comprehensive testing of expression semantics (arithmetic, logic, etc.) using the fully supported Pydantic-based model validation, without being blocked by the pending function generator implementation.

4. New Java Unit Tests

Several new JUnit tests were added to the Java codebase to verify specific generation logic:

• RosettaSwitchExpressionTest.java
• PythonFunctionBasicTest.java (and other targeted function tests)
• PythonBasicTypeGeneratorTest.java

Impact

• Developers: The CLI is now much more helpful for debugging Rosetta models, as it provides specific error locations during the build process.
• CI/CD: The restructured test suite is more modular and provides better granularity for identifying regressions.
• Maintainability: Moving away from complex functional tests toward type-condition-based tests ensures the test suite remains green while core generator features are still being matured.

Verification Results

• All JUnit tests in src/test/java passed.
• Python unit tests passed.
• CLI successfully validated and processed complex Rosetta models with the new "v2" logic.

[dschwartznyc]

Some of the tests were failing (they depended on function support which is forthcoming)- these have been fixed.