tests/test_pipeline_manager_vace.py (1)

147-151: Consider adding a test for load_params=None in the Krea branch.

The current tests cover vace_enabled=False but not the case where load_params itself is None. Based on the Krea implementation, when load_params=None:

• vace_path is set (14B checkpoint)
• vace_context_scale is not set (the inner if load_params: block is skipped)

This differs from passing {} where vace_context_scale defaults to 1.0. If this behavior is intentional, a test documenting it would be valuable.

📝 Optional: Add test for load_params=None

def test_no_load_params(self):
    """Krea branch with load_params=None should set vace_path but not vace_context_scale."""
    config = self._load_krea_config(None)
    assert "14B" in config["vace_path"]
    assert "vace_context_scale" not in config

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@tests/test_pipeline_manager_vace.py` around lines 147 - 151, Add a new unit
test in tests/test_pipeline_manager_vace.py to cover the Krea branch when
load_params is None: create a method (e.g., test_no_load_params) that calls the
existing helper _load_krea_config(None), asserts that the returned config
contains a vace_path (check that "14B" appears in config["vace_path"]) and
asserts that "vace_context_scale" is not present in the config; this mirrors the
behavior different from passing an empty dict and documents the intended
behavior alongside test_vace_disabled.