scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-09-16 23:41:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 102

fix(ci): register new update_settings helper methods as indirectly-tested

Browse source 
router_code_coverage.py detects test coverage via a static AST scan for
literal `.method_name(` calls in test files, not real coverage
instrumentation - it flagged _merge_default_litellm_params_setting and
_apply_optional_pre_call_checks_setting as untested even though they're
exercised through update_settings(default_litellm_params=...) /
(optional_pre_call_checks=...) in test_router.py, matching the existing
_merge_tools_from_deployment / _invalidate_access_groups_cache precedent for
private helpers only called indirectly.
This commit is contained in:
Krrish Dholakia 2026-07-13 18:51:45 -07:00
parent 9a513aba77
commit ca2fa744aa
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
tests/code_coverage_tests/router_code_coverage.py
View file

@ -80,6 +80,8 @@ ignored_function_names = [
"_override_vector_store_methods_for_router", # No-op placeholder, called during Router init
"_merge_tools_from_deployment", # Tested indirectly via _update_kwargs_with_deployment (test files lack "router" in name)
"_invalidate_access_groups_cache", # Tested indirectly via set_model_list, upsert_model etc. (test files lack "router" in name)
"_merge_default_litellm_params_setting", # Tested indirectly via update_settings(default_litellm_params=...)
"_apply_optional_pre_call_checks_setting", # Tested indirectly via update_settings(optional_pre_call_checks=...)
]