I’m building an open-source CLI for Toggl Track
Recently I’ve been improving real end-to-end testing for the CLI, not just mocked unit tests. The goal is to verify actual user paths through the binary
I’m using a dedicated test workspace and cleaning up created resources after tests. I’ve also reduced unnecessary API calls in both the implementation and the test flow.
The blocker now is API rate limiting.
While running live integration tests, I’m hitting Toggl API quota limits, which makes it difficult to keep validating real CLI behavior reliably in CI. I understand paid plans have higher limits, but I’m also not sure whether Premium
would actually be enough for sustained development and testing over time.
So I wanted to ask:
- Is there any way to get a sponsored or complimentary Toggl paid plan for this account for open-source development/testing?
- Even with Premium, is there a recommended approach for projects like this if the higher quota still may not be enough?
- For open-source tools integrating with Toggl, what’s the practical best practice here: a very small live smoke test set, some kind of sandbox strategy, or something else?
I’m not trying to stress the API unnecessarily. The goal is just to maintain a reliable open-source CLI with real integration coverage against a dedicated test workspace.
If someone from Toggl sees this, I’d appreciate any advice or support.