Add comprehensive tests for trajectory.compute() functions

[jon-myers]

Summary

The trajectory module has several compute() functions that currently lack comprehensive test coverage. We should add thorough tests for all compute functions to ensure reliability and catch regressions.

Scope

The following trajectory compute functions need test coverage:

Primary compute functions:

• compute_id7_id13() - Already has some basic tests but could be expanded
• compute_delegation_all_ids() - Has basic tests
• Other compute functions that may exist in the trajectory module

Test areas to cover:

1. Normal operation cases

   • Valid input data with expected outputs
   • Different trajectory types (vocal, instrumental)
   • Various data configurations

2. Edge cases

   • Empty trajectories
   • Missing required data fields
   • Boundary value conditions
   • Invalid input types

3. Error handling

   • Malformed input data
   • Missing dependencies
   • Invalid parameter combinations

4. Integration scenarios

   • How compute functions interact with other trajectory methods
   • Performance with large datasets
   • Memory usage patterns

Implementation Notes

• Look at existing tests in idtap/tests/trajectory_test.py for patterns
• Follow the established testing conventions in the codebase
• Consider parameterized tests for testing multiple scenarios efficiently
• Mock external dependencies where appropriate

Acceptance Criteria

• All trajectory compute functions have comprehensive test coverage
• Tests cover normal operation, edge cases, and error conditions
• Test suite continues to run efficiently (no significant performance impact)
• Documentation updated if new test patterns are established

Priority

Medium - These are core functions that would benefit from better test coverage to prevent regressions and ensure reliability.

📝 Created automatically after PyPI v0.1.9 release