Write table-driven tests

Write a table-driven test suite for the code below using the repository's existing test style. Cover the happy path, empty and nil input, boundaries, malformed data, and the reported regression. Avoid network and clock flakiness; inject or fake dependencies when needed. Each case name should describe the behavior. Do not change production behavior to make the test pass.

```
[CODE]
```