Files
cleveragents-core/features/module_coverage.feature
HAL9000 f808abff86 chore(ci): fix pre-commit hook failures
Fix JSON syntax errors in .devcontainer/devcontainer.json (removed
invalid JS-style // comments) and .devcontainer/opencode.json (removed
90+ trailing commas). Apply auto-fixes for end-of-file and trailing
whitespace issues across 100+ files. Fix SIM105 ruff violations in
benchmarks/core_circuit_breaker_bench.py (use contextlib.suppress).

Note: The security fix from issue #7478 (validate_path startswith bypass)
was already delivered to master in commit e18ac5f2. This PR as currently
structured is non-atomic (35 commits across 10+ issues) and needs
significant restructure before merge. This commit only addresses the
CI/pre-commit failures.

ISSUES CLOSED: #7478
2026-06-14 09:51:14 -04:00

47 lines
1.6 KiB
Gherkin

Feature: Module Entry Points Coverage
As a developer
I want to test all module entry points
So that module loading and execution paths are covered
Scenario: Test __main__ module execution
When I execute the __main__ module directly
Then the module should run successfully
Scenario: Test __main__ module with arguments
When I execute the __main__ module with arguments
Then the module should process arguments correctly
Scenario: Test __main__ module with keyboard interrupt
When I execute the __main__ module and interrupt it
Then the module should handle keyboard interrupt
Scenario: Test direct module imports
When I import all application modules directly
Then all modules should import without error
Scenario: Test exception hierarchy
When I test all exception classes
Then all exceptions should work correctly
Scenario: Test container with environment variables
Given environment variables are set
When I create a container
Then the container should use environment settings
Scenario: Test container without API keys
Given no API keys are configured
When I create a container
Then the container should handle missing keys
Scenario: Test settings validation
When I create settings with invalid values
Then validation should handle errors properly
Scenario: Test platform module functions
When I test platform module functions
Then all platform functions should work
Scenario: Test CLI shortcuts
When I use CLI shortcut commands
Then shortcuts should map to full commands