Module testing 

View fixtures for a sibling crate’s tests.

A ViewSurface only ever comes off an Arc<Workspace>, and the constructors that build one without a real machine are behind forge-workspace’s own test features. A crate testing a view would otherwise have to name that crate in its manifest to get one; this module is the way round, kept behind its own testing feature so a production build never sees it.

Every constructor here hands back its failure rather than panicking, so a caller that wants a panic is the one that asks for it.

Re-exports

use std::path::Path; 🔒

use std::sync::Arc; 🔒

use forge_primitives::SessionSlot; 🔒

use forge_primitives::tasks::Task; 🔒

use forge_primitives::tasks::TaskStatus; 🔒

use forge_primitives::CronEntry; 🔒

use forge_primitives::CronId; 🔒

use forge_primitives::CronKind; 🔒

use forge_workspace::ProjectKey; 🔒

use forge_workspace::Workspace; 🔒

use tokio::sync::mpsc; 🔒

use crate::SessionUpdate; 🔒

use crate::surface::PendingKind; 🔒

use crate::surface::ViewSurface; 🔒

use crate::transport::TransportState; 🔒

Structs

Fleet

A view surface over a stub workspace, plus the seeding a test needs to put a roster in front of it.

ViewFacts

The facts a session holds that no update stream carries, for a view’s fixture to seed. Every field is what the session reports: leaving one out is a session that has not reported it.

Constants

SEEDED_SESSION 🔒

The session id a seeded transcript belongs to. One per fleet is enough: a test that needs two reads two slots against their own files.

Functions

config 🔒

The forge.toml a fleet is built from: one [[orgs]] per entry, each project under its own directory so two projects never share a path.

Type Aliases

FixtureError

What a fixture hands back when it cannot build what was asked for.