Summary
Analog event control statements have limited test coverage, and some are documented as not yet implemented.
Current Status
From documentation:
@(initial_step), @(final_step) - supported
- Named events (
@foo) - not supported
- Monitored events (
@(cross(...))) - not supported
- Or events - not supported
Missing Test Coverage
Even for supported events, dedicated tests are limited:
Supported features needing tests
@(initial_step) - Basic and conditional usage
@(final_step) - Cleanup/finalization code
- Multiple
initial_step blocks in same module
Features to test when implemented
cross(expr, direction) - Zero crossing detection
above(expr, threshold) - Threshold crossing
- Timer events
Current State
- No dedicated test files for event handling in
openvaf/test_data/
- Events may be tested indirectly through integration tests
Suggested Action
- Add explicit tests for
initial_step and final_step behavior
- Add UI tests for proper error messages when unsupported events are used
- When implementing new events, add comprehensive tests
Summary
Analog event control statements have limited test coverage, and some are documented as not yet implemented.
Current Status
From documentation:
@(initial_step),@(final_step)- supported@foo) - not supported@(cross(...))) - not supportedMissing Test Coverage
Even for supported events, dedicated tests are limited:
Supported features needing tests
@(initial_step)- Basic and conditional usage@(final_step)- Cleanup/finalization codeinitial_stepblocks in same moduleFeatures to test when implemented
cross(expr, direction)- Zero crossing detectionabove(expr, threshold)- Threshold crossingCurrent State
openvaf/test_data/Suggested Action
initial_stepandfinal_stepbehavior