scriptoriumadmin/fabro
1
0
Fork 0
mirror of https://github.com/fabro-sh/fabro.git synced 2026-10-01 02:04:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Assert the graph name field in local_run_lifecycle

Browse source 
`ps --json` reports the digraph name as `workflow_graph_name` and reserves
`workflow_name` for an explicit `[workflow] name` (6a86ced77). That change
updated the ps tests but not this ignored e2e test, which still expected
the graph name under `workflow_name`. The test now asserts the contract
the ps tests assert: `workflow_name` is null for a bare graph file and
`workflow_graph_name` is the digraph name.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Bryan Helmkamp 2026-09-14 09:41:05 -06:00
parent b46ed0a429
commit e3ea3ff2e6
No known key found for this signature in database
1 changed files with 8 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
lib/apps/fabro-cli/tests/it/scenario/lifecycle.rs
View file

@ -49,10 +49,16 @@ fn local_run_lifecycle() {
.as_str()
.expect("run should have run_id")
.to_string();
// A bare `.fabro` file has no `[workflow] name`, so `ps --json` reports
// the digraph name only as `workflow_graph_name`.
assert!(
runs[0]["workflow_name"].is_null(),
"workflow_name should be null for a bare graph file: {ps_stdout}"
);
assert_eq!(
runs[0]["workflow_name"].as_str(),
runs[0]["workflow_graph_name"].as_str(),
Some("CommandPipeline"),
"workflow_name should be CommandPipeline"
"workflow_graph_name should be CommandPipeline: {ps_stdout}"
);
// 3. inspect <run_id> — JSON array with run_spec and conclusion