From f90151a0e4ea45ce5ce2c612ef0ee8c1fb0bf57c Mon Sep 17 00:00:00 2001 From: Maximilian Roos Date: Mon, 24 Nov 2025 19:09:12 -0800 Subject: [PATCH] docs: Clarify why progressive test allows verification failures MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Document that this test focuses on final output correctness while other tests (test_list_progressive_rendering_basic, test_list_progressive_dots_decrease) provide strict verification with .unwrap(). This makes the different testing philosophies explicit. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- tests/integration_tests/list_progressive.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tests/integration_tests/list_progressive.rs b/tests/integration_tests/list_progressive.rs index 385833617f..a5148ddf7a 100644 --- a/tests/integration_tests/list_progressive.rs +++ b/tests/integration_tests/list_progressive.rs @@ -86,11 +86,11 @@ fn test_list_progressive_rendering_stages() { let samples = output.samples(3); assert!(!samples.is_empty(), "Should get at least one sample stage"); - // If we have enough stages, use canonical verification - // (handles edge cases like fast completion gracefully) + // Best-effort verification: progressive rendering may complete too quickly to observe on + // fast CI machines. Other tests (test_list_progressive_rendering_basic, + // test_list_progressive_dots_decrease) provide strict verification with .unwrap(); + // this test focuses on final output correctness. if output.stages.len() >= 2 { - // verify_progressive_filling() returns Err if progressive rendering wasn't observable, - // which is acceptable on fast CI machines - just skip the assertion in that case let _ = output.verify_progressive_filling(); }