AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: go-synctest-synthetic-time-concurrency

Go 1.24 Synctest Synthetic Time Concurrency Invariant

Mandates encapsulating asynchronous and time-dependent concurrent test suites inside Go 1.24 synthetic time bubbles via testing/synctest. Eliminates non-deterministic wall-clock sleeps, instantaneous virtualized timer resolution, and guarantees that goroutine deadlocks and leaks trigger immediate, repeatable panics prior to production deployment.

Prohibited Anti-Pattern: Arbitrary Wall-Clock Sleeping and Non-Deterministic Polling in Concurrent Tests

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Go 1.24 Synctest Synthetic Time Concurrency Invariant - Mandates encapsulating asynchronous and time-dependent concurrent test suites inside Go 1.24 synthetic time bubbles via testing/synctest. Eliminates non-deterministic wall-clock sleeps, instantaneous virtualized timer resolution, and guarantees that goroutine deadlocks and leaks trigger immediate, repeatable panics prior to production deployment.
globs: **/*_test.go
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/go-synctest-synthetic-time-concurrency"
---

# Go 1.24 Synctest Synthetic Time Concurrency Invariant

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Arbitrary Wall-Clock Sleeping and Non-Deterministic Polling in Concurrent Tests

## System Constraints
You are a Principal Software Architect enforcing the Go 1.24 Synctest Synthetic Time Concurrency Invariant. Reject all wall-clock sleep loops (e.g., time.Sleep with arbitrary durations) and flaky polling loops in asynchronous unit and subsystem tests. Enforce testing/synctest isolation bubbles with synctest.Run and synctest.Wait to verify time-sensitive concurrent primitives deterministically. Ensure that any goroutines spawned within a bubble are fully resolved or intentionally blocked before the bubble exits.

## Strict Guidelines
- Engineers MUST ALWAYS encapsulate concurrent, time-sensitive unit tests inside `synctest.Run(func() { ... })` when testing timeouts, backoffs, debouncers, and tickers.
- Engineers MUST NOT introduce non-deterministic wall-clock delays (`time.Sleep`) or unbounded polling loops (`for { select { ... } }`) in test assertions.
- Engineers MUST invoke `synctest.Wait()` to durably ensure all goroutines inside the synthetic bubble have settled into a blocked state before asserting state mutations.
- Code SHOULD rely on the synthetic bubble's automatic virtual clock advancement when all goroutines within the bubble are idle or waiting on timers.
- Services MUST NOT leak goroutines beyond the boundary of `synctest.Run`; if unmanaged background goroutines outlive the synthetic bubble, synctest will panic and fail the build immediately.
- Components NEVER bridge external non-synthetic channels or system timers directly into a `synctest.Run` scope without proper isolation.

## Bad vs Good Implementations
### Deterministic Concurrency Testing with testing/synctest

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using real wall-clock sleeps causes flaky test runs under high CI load, slows suite execution, and conceals subtle race conditions and deadlocks when timers fire out of expected sequence.
```go
package service_test

import (
	"sync/atomic"
	"testing"
	"time"
)

func TestDebouncedEmitter_Flaky(t *testing.T) {
	var emitted atomic.Int32
	emitter := NewDebouncer(500 * time.Millisecond, func() {
		emitted.Add(1)
	})

	emitter.Trigger()
	emitter.Trigger()

	// ANTI-PATTERN: Wall-clock sleeping induces flakiness on busy CI runners
	// and dramatically slows down execution across thousands of tests.
	time.Sleep(600 * time.Millisecond)

	if got := emitted.Load(); got != 1 {
		t.Fatalf("expected 1 emission, got %d", got)
	}
}
```

#### Production Standard (Correct)
> **Standard**: Running inside synctest.Run provisions a virtualized clock bubble. time.Sleep executes instantaneously without wall-clock latency, and synctest.Wait ensures all bubble goroutines settle deterministically.
```go
package service_test

import (
	"sync/atomic"
	"testing"
	"testing/synctest"
	"time"
)

func TestDebouncedEmitter_Synctest(t *testing.T) {
	synctest.Run(func() {
		var emitted atomic.Int32
		emitter := NewDebouncer(500*time.Millisecond, func() {
			emitted.Add(1)
		})

		emitter.Trigger()
		emitter.Trigger()

		// Wait for goroutines in bubble to block, then step virtual time
		synctest.Wait()
		time.Sleep(500 * time.Millisecond) // Advances synthetic virtual time instantaneously
		synctest.Wait()

		if got := emitted.Load(); got != 1 {
			t.Fatalf("expected 1 emission, got %d", got)
		}
	})
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Go Toolchain Controller
Orchestrates Go compilation and execution passes with GOEXPERIMENT=synctest validation flags.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Goroutine Leak Detection
Complements synctest by analyzing test run teardowns to verify no unmanaged goroutines escape execution bubbles.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Go 1.24 Synctest Synthetic Time Concurrency Invariant

Go 1.24 Synctest Synthetic Time Concurrency Invariant defines an industrial-grade behavioral standard for backend engineering. Mandates encapsulating asynchronous and time-dependent concurrent test suites inside Go 1.24 synthetic time bubbles via testing/synctest. Eliminates non-deterministic wall-clock sleeps, instantaneous virtualized timer resolution, and guarantees that goroutine deadlocks and leaks trigger immediate, repeatable panics prior to production deployment. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Arbitrary Wall-Clock Sleeping and Non-Deterministic Polling in Concurrent Tests Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftArbitrary Wall-Clock Sleeping and Non-Deterministic Polling in Concurrent TestsCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS encapsulate concurrent, time-sensitive unit tests inside `synctest.Run(func() { ... })` when testing timeouts, backoffs, debouncers, and tickers.

Engineers MUST ALWAYS encapsulate concurrent, time-sensitive unit tests inside `synctest.Run(func() { ... })` when testing timeouts, backoffs, debouncers, and tickers.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT introduce non-deterministic wall-clock delays (`time.Sleep`) or unbounded polling loops (`for { select { ... } }`) in test assertions.

Engineers MUST NOT introduce non-deterministic wall-clock delays (`time.Sleep`) or unbounded polling loops (`for { select { ... } }`) in test assertions.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Engineers MUST invoke `synctest.Wait()` to durably ensure all goroutines inside the synthetic bubble have settled into a blocked state before asserting state mutations.

Engineers MUST invoke `synctest.Wait()` to durably ensure all goroutines inside the synthetic bubble have settled into a blocked state before asserting state mutations.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Code SHOULD rely on the synthetic bubble's automatic virtual clock advancement when all goroutines within the bubble are idle or waiting on timers.

Code SHOULD rely on the synthetic bubble's automatic virtual clock advancement when all goroutines within the bubble are idle or waiting on timers.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Services MUST NOT leak goroutines beyond the boundary of `synctest.Run`

Services MUST NOT leak goroutines beyond the boundary of `synctest.Run`; if unmanaged background goroutines outlive the synthetic bubble, synctest will panic and fail the build immediately.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
6

Components NEVER bridge external non-synthetic channels or system timers directly into a `synctest.Run` scope without proper isolation.

Components NEVER bridge external non-synthetic channels or system timers directly into a `synctest.Run` scope without proper isolation.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Go 1.24 Synctest Synthetic Time Concurrency Invariant critical for AI coding assistants?

Mandates encapsulating asynchronous and time-dependent concurrent test suites inside Go 1.24 synthetic time bubbles via testing/synctest. Eliminates non-deterministic wall-clock sleeps, instantaneous virtualized timer resolution, and guarantees that goroutine deadlocks and leaks trigger immediate, repeatable panics prior to production deployment. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Arbitrary Wall-Clock Sleeping and Non-Deterministic Polling in Concurrent Tests) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

Go