flowforge-testing

Flow Forge Test Case Generation & Execution

1. Preflight

1. Locate the flow-forge repository root: prefer flowforge_root from flowforge.config.yaml; otherwise use the parent directory of this skill. Verify the python/ and shared/ layout exists.
2. Load flowforge.config.yaml. If it does not exist, copy it from flowforge.config.yaml.example and ask the user for the key settings (language, Python environment, executor defaults).
3. Resolve the Python interpreter by running scripts/resolve_python.py. Resolution order: python_path (explicit) -> configured mode (conda/venv/system) -> automatic detection. The chosen interpreter must be able to import requests, openpyxl and yaml.
4. If dependencies are missing, ask the user to install them in the configured environment (for example conda activate api_test && pip install -r python/requirements.txt). Never install packages into the conda base environment.
5. Check the executor configuration (python/env.yml and python/env-{envName}.yml). Fill in missing app baseURL, login settings and processor_configs entries from the user's deployment notes or documentation. If credentials are still missing, ask the user once for them; never guess or fabricate credentials.
6. Prepare middleware when needed: run python/tools/h2/init_h2.py for H2; start the system-under-test or middleware services as background subprocesses and record their PIDs so the main flow never blocks. If a service cannot be started automatically, report it to the user.

2. Inputs

• Requirement documents: .md / .txt / .pdf, one or more. Analyze each document separately, then merge and deduplicate by content (business flows, roles, constraints, exceptions).
• API documents: OpenAPI 3.0 (JSON/YAML) or Markdown tables, one or more. Merge and deduplicate interfaces by (path, method).
• Optional supplementary inputs: table structures/DDL, business rules, existing test cases, middleware connection information, deployment notes. Use them during requirement analysis and case generation; do not output them as separate artifacts.