Files
OmniRoute/tests/integration
Diego Rodrigues de Sa e Souza 9f14c1294a test: align stale integration tests surfaced post-v3.8.28 on main (#4129)
Two integration tests were red on `main` after the v3.8.28 release merged.
Integration tests do not gate PR->release, so these only surfaced on
push->main once the cycle's changes landed:

- v1-contracts-behavior count_tokens expected 3 (the old ceil(chars/4)
  heuristic). #4087 switched the estimator to real tiktoken (countTextTokens):
  "abcd" => 1, "12345678" => 3, total 4. Assertion updated to the verified
  tiktoken total.

- combo-routing-e2e round-robin tests assumed one-request-per-target rotation,
  but stickyRoundRobinLimit defaults to 3 and sticky batching has applied to
  combos since v3.8.26 (#3846). Both tests now drive enough requests to observe
  the batched rotation: round-robin cycles openai x3 -> claude x3 -> gemini x3;
  the strategy-update test proves round-robin took over by reaching claude on
  the 4th post-update request (a target priority would never select).

Test-only; no production behavior change. Verified locally: both files green.
2026-06-17 23:20:17 -03:00
..
2026-05-26 23:51:47 -03:00
2026-05-26 23:51:47 -03:00
2026-04-30 01:27:03 -03:00
2026-06-04 20:05:38 -03:00
2026-05-10 00:55:06 -03:00
2026-05-23 01:46:59 -03:00
2026-06-09 15:56:24 -03:00
2026-06-12 23:49:22 -03:00