ReplProcessSignalOptions
Options for one ReplProcessSignalHarness.
- Kind:
Class - Namespace: Repl.Testing
- Assembly:
Repl.Testing - Source: src/Repl.Testing/ReplProcessSignalOptions.cs
Signature
Section titled “Signature”public sealed class ReplProcessSignalOptionsInheritance
Section titled “Inheritance”Properties
Section titled “Properties”NormalizeAnsi
Section titled “NormalizeAnsi”Strips ANSI escape sequences and carriage returns from captured text, so an assertion does not depend on whether the run decided to colour its output. Defaults to true.
public bool NormalizeAnsi { get; set; }Returns
Section titled “Returns”Platform
Section titled “Platform”The platform whose decisions apply. Defaults to Current.
public ReplPlatformProfile Platform { get; set; }Returns
Section titled “Returns”RegistrationFault
Section titled “RegistrationFault”Makes the next registration attempt fail with this exception, so a test can assert that automatic handling degrades to caller-owned and says so, rather than taking it on trust. No supported platform refuses a registration on demand, so this is the only way to reach that path. null to let registration proceed normally.
public Exception? RegistrationFault { get; set; }Returns
Section titled “Returns”RunTimeout
Section titled “RunTimeout”How long a run may take before Completion fails with a TimeoutException. A signal test starts a run that blocks until it is cancelled, so this is what turns “the signal never arrived” into a failing test instead of a hung one. Defaults to 10 seconds. Use InfiniteTimeSpan to disable it.
Measured against the clock, not against the run agreeing to stop: a command that never observes its cancellation token cannot be interrupted, so the harness abandons it rather than waiting. The command keeps running — nothing here can kill it — and because it still holds a place in the process-wide signal epoch, disposal reports it rather than letting later signal tests inherit it. Disabling the timeout gives that up: a run that never ends then hangs both its completion and the harness’s disposal. That is why it takes InfiniteTimeSpan and nothing else — zero and negatives are refused rather than read as “no timeout”, so the one setting that can hang a suite has to be asked for in as many words.
public TimeSpan RunTimeout { get; set; }