Coroutine scheduling tests
Section titled “Coroutine scheduling tests”Inno.Core.Coroutines.Tests verifies the Coroutines contracts through their public entry points. Use this page to locate relevant assertions; it is not a report that these tests passed for your current change.
Behavior covered
Section titled “Behavior covered”The scheduler tests distinguish the next tick from elapsed-time waits, evaluate wait predicates, and stop only the selected coroutine. These cases exercise the managed scheduler rather than a product frame loop.
Environment and execution
Section titled “Environment and execution”The project declares the domain validation layer. Use the shared validation workflow to select its actual dependencies and environment. Inspect the pinned project file for package and project references.
A focused diagnostic from the engine root is:
dotnet test tests/core/Inno.Core.Coroutines.Tests/Inno.Core.Coroutines.Tests.csproj --configuration Debug --disable-build-servers -m:1 -nodeReuse:falseUse --filter FullyQualifiedName~MethodName to investigate one case. A filtered run does not replace the obligations in the validation plan. Restore the declared SDK, packages and any tool/process prerequisites before executing; preserve cancellation, thread and cleanup requirements.
Scenario reference
Section titled “Scenario reference”These representative methods are preserved from the original reference and checked against the pinned source. The linked files contain all assertions and parameterized cases.
Coroutine Scheduler
Section titled “Coroutine Scheduler”Read the assertions. Representative entry points:
StartCoroutine_NullYield_RunsOnNextTickWaitForSeconds_WaitsByTimeWaitUntil_And_WaitWhile_WorkStopCoroutine_StopsTarget
Extend safely
Section titled “Extend safely”Follow the shared suite-maintenance guidance. Preserve this suite’s owner-thread, resource-release and failure assertions when adding cases.