The current AudioManager tests cover the happy path for connect() and several playback state transitions, but they do not cover a failed entersState() call during connection startup.
That path is important because connect() sets state to connecting, creates a voice connection, subscribes the audio player, and then awaits readiness. A regression test should pin the behavior when readiness fails or times out.
Acceptance Criteria
Add a focused Jest test where entersState() rejects.
Assert the observable state/resource behavior after the failed connect() attempt.
Keep the test local to tests/audio-manager.test.ts; no new dependencies.
### Description
The current `AudioManager` tests cover the happy path for `connect()` and several playback state transitions, but they do not cover a failed `entersState()` call during connection startup.
That path is important because `connect()` sets state to `connecting`, creates a voice connection, subscribes the audio player, and then awaits readiness. A regression test should pin the behavior when readiness fails or times out.
### Acceptance Criteria
- Add a focused Jest test where `entersState()` rejects.
- Assert the observable state/resource behavior after the failed `connect()` attempt.
- Keep the test local to `tests/audio-manager.test.ts`; no new dependencies.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
The current
AudioManagertests cover the happy path forconnect()and several playback state transitions, but they do not cover a failedentersState()call during connection startup.That path is important because
connect()sets state toconnecting, creates a voice connection, subscribes the audio player, and then awaits readiness. A regression test should pin the behavior when readiness fails or times out.Acceptance Criteria
entersState()rejects.connect()attempt.tests/audio-manager.test.ts; no new dependencies.