332 lines
27 KiB
JSON
332 lines
27 KiB
JSON
{
|
|
"request": {
|
|
"campaign": "SYNTHETIC",
|
|
"suite": "BALANCED-IMPLEMENTATION",
|
|
"cases": [
|
|
{
|
|
"alias": "CASE-0001",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use the reset RPC adapter with an in-memory transport stub and deterministic response fixtures.",
|
|
"success_criteria": "Send a reset RPC, observe the returned status object and reset counter, and assert acceptance or rejection plus the expected counter change. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0002",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use a pulse generator and an oscilloscope adapter connected to the reset and ready lines; clear captured samples between cases.",
|
|
"success_criteria": "Apply a reset pulse, capture both electrical traces, measure their relative transition times, and assert the supplied timing bound and recovery sequence. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0003",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0004",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0005",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use the reset RPC adapter with an in-memory transport stub and deterministic response fixtures.",
|
|
"success_criteria": "Send a reset RPC, observe the returned status object and reset counter, and assert acceptance or rejection plus the expected counter change. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0006",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use a pulse generator and an oscilloscope adapter connected to the reset and ready lines; clear captured samples between cases.",
|
|
"success_criteria": "Apply a reset pulse, capture both electrical traces, measure their relative transition times, and assert the supplied timing bound and recovery sequence. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0007",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0008",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0009",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use the reset RPC adapter with an in-memory transport stub and deterministic response fixtures.",
|
|
"success_criteria": "Send a reset RPC, observe the returned status object and reset counter, and assert acceptance or rejection plus the expected counter change. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0010",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use a pulse generator and an oscilloscope adapter connected to the reset and ready lines; clear captured samples between cases.",
|
|
"success_criteria": "Apply a reset pulse, capture both electrical traces, measure their relative transition times, and assert the supplied timing bound and recovery sequence. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0011",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0012",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0013",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use the reset RPC adapter with an in-memory transport stub and deterministic response fixtures.",
|
|
"success_criteria": "Send a reset RPC, observe the returned status object and reset counter, and assert acceptance or rejection plus the expected counter change. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0014",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use a pulse generator and an oscilloscope adapter connected to the reset and ready lines; clear captured samples between cases.",
|
|
"success_criteria": "Apply a reset pulse, capture both electrical traces, measure their relative transition times, and assert the supplied timing bound and recovery sequence. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0015",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0016",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0017",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use the reset RPC adapter with an in-memory transport stub and deterministic response fixtures.",
|
|
"success_criteria": "Send a reset RPC, observe the returned status object and reset counter, and assert acceptance or rejection plus the expected counter change. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0018",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use a pulse generator and an oscilloscope adapter connected to the reset and ready lines; clear captured samples between cases.",
|
|
"success_criteria": "Apply a reset pulse, capture both electrical traces, measure their relative transition times, and assert the supplied timing bound and recovery sequence. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0019",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0020",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0021",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use the reset RPC adapter with an in-memory transport stub and deterministic response fixtures.",
|
|
"success_criteria": "Send a reset RPC, observe the returned status object and reset counter, and assert acceptance or rejection plus the expected counter change. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0022",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use a pulse generator and an oscilloscope adapter connected to the reset and ready lines; clear captured samples between cases.",
|
|
"success_criteria": "Apply a reset pulse, capture both electrical traces, measure their relative transition times, and assert the supplied timing bound and recovery sequence. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0023",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0024",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0025",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use a pulse generator and an oscilloscope adapter connected to the reset and ready lines; clear captured samples between cases.",
|
|
"success_criteria": "Apply a reset pulse, capture both electrical traces, measure their relative transition times, and assert the supplied timing bound and recovery sequence. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0026",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0027",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0028",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0029",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0030",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0031",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0032",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0033",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0034",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Load offline reset-analysis report files through the same report parser and a rule-to-severity policy fixture; do not execute the target.",
|
|
"success_criteria": "Parse report entries, count reset-related findings for the requested rule and severity, and assert the count and report location against the policy fixture. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0035",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0036",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "nominal"
|
|
},
|
|
{
|
|
"alias": "CASE-0037",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
},
|
|
{
|
|
"alias": "CASE-0038",
|
|
"description": "Verify reset recovery under a selected operating condition. Preserve each objective independently; similar reset terminology does not establish common test machinery.",
|
|
"preconditions": "Use concurrent producer and consumer task drivers, queue-depth instrumentation, and sequence-number recording around a resettable bounded queue.",
|
|
"success_criteria": "Drive the bounded queue through reset while producers run, observe depth and ordered delivery, and assert rejected writes and recovery after draining. Vary the supplied expected values while reusing these observations.",
|
|
"case_type": "fault injection"
|
|
}
|
|
],
|
|
"routing": {
|
|
"allow_external": true,
|
|
"allowed_external_providers": [
|
|
"claude"
|
|
]
|
|
},
|
|
"execution": {
|
|
"strategy": "whole_suite",
|
|
"max_seconds": 900,
|
|
"max_cost_usd": 5
|
|
}
|
|
},
|
|
"expected_implementation_family": {
|
|
"CASE-0001": "command",
|
|
"CASE-0002": "timing",
|
|
"CASE-0003": "report",
|
|
"CASE-0004": "queue",
|
|
"CASE-0005": "command",
|
|
"CASE-0006": "timing",
|
|
"CASE-0007": "report",
|
|
"CASE-0008": "queue",
|
|
"CASE-0009": "command",
|
|
"CASE-0010": "timing",
|
|
"CASE-0011": "report",
|
|
"CASE-0012": "queue",
|
|
"CASE-0013": "command",
|
|
"CASE-0014": "timing",
|
|
"CASE-0015": "report",
|
|
"CASE-0016": "queue",
|
|
"CASE-0017": "command",
|
|
"CASE-0018": "timing",
|
|
"CASE-0019": "report",
|
|
"CASE-0020": "queue",
|
|
"CASE-0021": "command",
|
|
"CASE-0022": "timing",
|
|
"CASE-0023": "report",
|
|
"CASE-0024": "queue",
|
|
"CASE-0025": "timing",
|
|
"CASE-0026": "report",
|
|
"CASE-0027": "queue",
|
|
"CASE-0028": "report",
|
|
"CASE-0029": "queue",
|
|
"CASE-0030": "report",
|
|
"CASE-0031": "queue",
|
|
"CASE-0032": "report",
|
|
"CASE-0033": "queue",
|
|
"CASE-0034": "report",
|
|
"CASE-0035": "queue",
|
|
"CASE-0036": "queue",
|
|
"CASE-0037": "queue",
|
|
"CASE-0038": "queue"
|
|
},
|
|
"expected_natural_sizes": [
|
|
6,
|
|
7,
|
|
11,
|
|
14
|
|
]
|
|
}
|