Package org.fhirfrog.frog.testplan

Class TestPlanProvider

java.lang.Object

org.fhirfrog.frog.testplan.TestPlanProvider

public class TestPlanProvider
extends Object

JUnit 5 dynamic test provider for recursive TestPlan execution. Expands test suites lazily with cycle detection and optional PlantUML recording.

Before execution begins, all referenced TestScripts and nested TestPlans are assembled into a local resource map. Unresolvable references are detected and reported before any test executes.

Nested Class Summary

Nested Classes

Modifier and Type	Class	Description
static class	TestPlanProvider.TestCaseResult	One test case's result from executeAll(org.fhirfrog.frog.testplan.TestPlanResource, org.fhirfrog.frog.testplan.VariableContext) - the programmatic counterpart to what generateTests(org.fhirfrog.frog.testplan.TestPlanResource, org.fhirfrog.frog.testplan.VariableContext)'s JUnit DynamicTests only report as pass/fail.
static class	TestPlanProvider.TestCaseSummary	One test case's static structure from discover(org.fhirfrog.frog.testplan.TestPlanResource) - the same identifying/dependency fields as TestPlanProvider.TestCaseResult, minus the execution-only ones (success, message, testReport) that don't exist until something has actually run.

Constructor Summary

Constructors

Constructor	Description
TestPlanProvider(String serverUrl, Path fixtureBasePath)

Method Summary

Modifier and Type	Method	Description
List<TestPlanProvider.TestCaseSummary>	discover(TestPlanResource testPlan)	Browses a TestPlan's structure - ids, display names, authored descriptions, dependency edges, and consumed/produced variable names - without executing anything: no TestScriptEngine, no network call, no VariableContext mutation.
List<TestPlanProvider.TestCaseResult>	executeAll(TestPlanResource testPlan, VariableContext context)	Programmatic (non-JUnit) counterpart to generateTests(org.fhirfrog.frog.testplan.TestPlanResource, org.fhirfrog.frog.testplan.VariableContext), for a caller that wants full per-assertion result detail directly rather than JUnit DynamicNodes a JUnit engine executes lazily - e.g. a REST-backed runner like frog-runner, which reports a real TestReport per test case the same way it already does for flat TestScripts, not just a pass/fail from a discarded assertTrue.
List<TestPlanProvider.TestCaseResult>	executeAll(TestPlanResource testPlan, VariableContext context, Consumer<TestPlanProvider.TestCaseResult> onResult)	Same as executeAll(TestPlanResource, VariableContext), but invokes onResult the moment each test case finishes rather than only returning the full list once every case has run - lets a caller (e.g. frog-runner, executing a TestPlan on a background thread) show genuine incremental progress instead of an all-or-nothing jump to 100% once this returns.
Stream<org.junit.jupiter.api.DynamicNode>	generateTests(TestPlanResource testPlan, VariableContext context)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

TestPlanProvider

public TestPlanProvider(String serverUrl,
 Path fixtureBasePath)

Method Details

generateTests

public Stream<org.junit.jupiter.api.DynamicNode> generateTests(TestPlanResource testPlan,
 VariableContext context)

executeAll

public List<TestPlanProvider.TestCaseResult> executeAll(TestPlanResource testPlan,
 VariableContext context)

Programmatic (non-JUnit) counterpart to generateTests(org.fhirfrog.frog.testplan.TestPlanResource, org.fhirfrog.frog.testplan.VariableContext), for a caller that wants full per-assertion result detail directly rather than JUnit DynamicNodes a JUnit engine executes lazily - e.g. a REST-backed runner like frog-runner, which reports a real TestReport per test case the same way it already does for flat TestScripts, not just a pass/fail from a discarded assertTrue. Same dependency ordering, cycle detection, and variable threading as generateTests(org.fhirfrog.frog.testplan.TestPlanResource, org.fhirfrog.frog.testplan.VariableContext) - suite nesting is flattened into one ordered list (suite-tree-shaped results are a GUI-visualization concern, not yet needed here).

executeAll

public List<TestPlanProvider.TestCaseResult> executeAll(TestPlanResource testPlan,
 VariableContext context,
 Consumer<TestPlanProvider.TestCaseResult> onResult)

Same as executeAll(TestPlanResource, VariableContext), but invokes onResult the moment each test case finishes rather than only returning the full list once every case has run - lets a caller (e.g. frog-runner, executing a TestPlan on a background thread) show genuine incremental progress instead of an all-or-nothing jump to 100% once this returns.

discover

public List<TestPlanProvider.TestCaseSummary> discover(TestPlanResource testPlan)

Browses a TestPlan's structure - ids, display names, authored descriptions, dependency edges, and consumed/produced variable names - without executing anything: no TestScriptEngine, no network call, no VariableContext mutation. Lets a caller (e.g. frog-runner's discovery view) show what a TestPlan run *would* do before committing to actually running it. Same dependency-ordering and suite-flattening as executeAll(org.fhirfrog.frog.testplan.TestPlanResource, org.fhirfrog.frog.testplan.VariableContext) - the two return cases in the same order, just with execution-only fields (success/message/testReport) absent since nothing ran.