Files
Chronos/tests/Chronos.Tools.Tests/TestTimingTests.cs
T
Alby96andClaude Opus 5.5 8566072c9a
CI / Build and test (pull_request) Successful in 8m3s
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 14s
CI / PostgreSQL 16 integration (pull_request) Successful in 5m56s
CI / PostgreSQL 17 integration (pull_request) Successful in 6m5s
CI / Docker image (pull_request) Successful in 1m18s
test: stretch timed budgets on the shared CI runner
The owner's runner shares its CPU and disks with Gitea and the server's other
containers, so the 100k-frame bulk insert took 10-19 s against 15 s from one
run to the next. CHRONOS_TEST_TIME_FACTOR (default 1) stretches the timed
tests' budgets; CI and release set 3, the weekly performance gates keep them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 12:19:36 +02:00

19 lines
552 B
C#

using Chronos.Testing;
namespace Chronos.Tools.Tests;
/// <summary>Time budgets stretch only by an explicit factor of at least 1 (BRIEF §20.1, amended 2026-10-23, R3).</summary>
public sealed class TestTimingTests
{
[Theory]
[Case("3", 3.0)]
[Case("1.5", 1.5)]
[Case(null, 1.0)]
[Case("", 1.0)]
[Case("0.5", 1.0)]
[Case("fast", 1.0)]
[Case("Infinity", 1.0)]
public void TheFactorIsReadInvariantlyAndNeverShrinksABudget(string? value, double expected) =>
Assert.Equal(expected, TestTiming.Parse(value));
}