Skip to content

Reporting

These three skills consolidate results into a final document. None of them tests again or navigates the application: they only compile what was already produced earlier. All of them generate a new timestamped file — they never overwrite a previous report, so the full history is preserved.


lippia-neo-write-test-report

When to use it

When there are already results from manual exploratory testing and automation/healing results, and you need to compile a final report (executive summary, defect log, coverage analysis). It's used when asking for the final report/summary after running the tests, or to consolidate manual and automated results into a single document without losing history.

Invocation example
{
  "input": {
    "us_id": "PA-US-02",
    "manual_results": { "...": "output de lippia-neo-run-manual-testing" },
    "automation_results": [
      { "label": "post-fix", "run": { "...": "output de lippia-neo-run-and-heal" } }
    ],
    "environment": {
      "APP_BASE_URL": "https://staging.miapp.com"
    }
  },
  "config": {
    "reports_dir": "test-results/reports/"
  }
}
Input Type Description
input.us_id Required Story identifier, used to name the report.
input.manual_results Required Results of the manual exploratory testing.
input.automation_results Required Automation + healing results; each entry can include label (pre-fix/post-fix/regresion-modulo/smoke), description, run (the output of lippia-neo-run-and-heal), or snapshot_path (a pre-fix snapshot .json). If there are "pre-fix" and "post-fix" entries, the before/after diff section is generated automatically; if there are equivalent competing runs, the most recent one wins.
input.environment Required APP_BASE_URL and browsers run (chromium / firefox / api).
config.reports_dir Required From qa-stack.yaml (defaults to test-results/reports/).
input.user_story_path Optional Path to the source story's .md file; null if it came from a cloud ticket.
input.bug_id Optional If present, it's added to the report's file name.
input.source_kind / input.source_url Optional Where the story came from (local/jira/azure-devops) and the ticket URL, when it's not local.
input.acceptance_criteria Optional Real acceptance criteria; without this, the coverage section is marked "not evaluable" instead of inferring it from the tests themselves.

Output

Field Description
report_path Path of the generated .md file.
overall_status passed / failed / blocked (blocked is due to an environment/config cause, failed is the product actually failing).
defects bug_id, severity (critical/high/medium/low), title.
coverage Criteria covered against input.acceptance_criteria, automation implemented vs. verified green, gaps.
summary Planned/executed totals and overall quality assessment.
Chains with

Consumes the manual output of lippia-neo-run-manual-testing and the automation output of lippia-neo-run-and-heal; in lippia-neo-meta-run-user-story-e2e it's step 6, the close of the flow.


lippia-neo-write-generation-report

When to use it

When test files were generated or expanded and you need to report it without running them as part of the same task — it compiles a report from the generation output (generated/skipped files, warnings) plus the context that justified generating them. It's an independent task: it doesn't assume a specific previous/next pipeline, skill, or plan. Unlike lippia-neo-write-test-report, it never reports an execution overall_status (passed/failed/ blocked), because it doesn't run anything.

Invocation example
{
  "input": {
    "generated_tests": {
      "status": "success",
      "generated_files": [
        { "path": "tests/checkout.spec.ts" }
      ]
    }
  },
  "config": {
    "reports_dir": "test-results/reports/"
  }
}
Input Type Description
input.generated_tests Required Output of any generation step: { status, generated_files, skipped_scenarios, warnings }.
config.reports_dir Required From qa-stack.yaml (defaults to test-results/reports/).
input.existing_tests Optional If a coverage search was run before.
input.context Optional Free-form justification of why the tests were generated (it can come from a bug reproduction, an exploration, or free text).
input.task_id Optional Task/story/ticket identifier, used in the file name; if missing, a generic name is generated.
input.task_path Optional Path to a source file (story, ticket, spec), referenced in the header if present.

Output

Field Description
report_path Path of the generated .md file.
status generated / partial / aborted (mirrors the generation status; never passed/failed).
generated_files path, test_case_id, suite_type (fe/be).
summary Totals (existing tests if applicable, generated/expanded files) and gaps.
Chains with

Deliberately independent; its "Next steps" section recommends running the generated_files and, if appropriate, then generating a results report with lippia-neo-write-test-report once a real run exists.


lippia-neo-write-exploratory-testing-report

When to use it

When a set of charter-style exploration sessions (lippia-neo-run-exploratory-session) has finished and you need a single consolidated portfolio report, with scope, coverage, findings, blocked or unselected areas, open questions, opportunities, and suggested follow-up charters. It doesn't navigate the app or test again — it consolidates already-existing sources. It also doesn't impose a risk scoring or fill in missing severities: anything that isn't classified stays as unclassified. It generates a timestamped .md and .json in <exploratory_dir>/<artifact_scope_id>/.

Invocation example
{
  "input": {
    "artifact_scope_id": "PORTFOLIO-2026-Q1",
    "portfolio": {
      "charters_planned": 5
    },
    "sessions": []
  },
  "config": {
    "paths": {
      "exploratory_dir": "exploration/"
    }
  }
}
Input Type Description
input.artifact_scope_id Required Identifier of the scope/portfolio.
input.portfolio Required Data on the planned portfolio/charters (including unselected areas, if any).
input.sessions Required Real outputs of the lippia-neo-run-exploratory-session sessions to consolidate.
config.paths.exploratory_dir Required Root output directory.
input.report_language Optional Defaults to es (the visible Markdown is monolingual; the JSON enums aren't translated).

Output

Field Description
artifact_scope_id, report_path, report_json_path
overall_status completed (all charters complete) / partial (at least one complete and another blocked or in_progress) / blocked (none complete). An in_progress session counts as not completed, never as covered.
charters_planned, charters_completed, charters_blocked
total_findings, findings_by_classification, findings_by_severity (critical/high/medium/low/info/unclassified)
areas_not_covered, suggested_follow_up_charters
Chains with

Consumes the outputs of one or more lippia-neo-run-exploratory-session runs; it's the final step of lippia-neo-meta-run-exploratory-testing.