Back to catalogue

Webapp Testing Pipeline

Developer Official v1.0.21

Plan test cases, write and execute tests, report failures, and fix issues in an automated cycle

by skrptiq

automation loops quality-assurance testing webapp
workflow Updated 17 July 2026 9 nodes 1 download

Sign in to import this skrpt into your workspace.

Sign in
What's included 9 nodes
1 workflow 3 skills 4 prompts 1 asset
workflow (1)

Webapp Testing Pipeline

Plan test cases, write and execute tests, report failures, and fix issues in an automated cycle

skills (3)

Fix Verification

Verifies that a code fix resolves the failing test and determines whether the fix cycle should continue

Test Reporting

Aggregates test results into a severity-ranked report with failure analysis and recommendations

Test Writing

Writes executable test code for a single test case using the project's testing framework

prompts (4)

Execute Test

Runs a test case and records the result with structured pass/fail output

Report Test Results

Aggregates test results into a severity-ranked quality report

Verify Fix

Evaluates whether a code fix resolves the failing test and decides if the fix cycle should continue

Write Test

Writes executable test code for a single test case

asset (1)

Test Plan Template

Structured template for organizing test cases by category and priority

Requirements 1 service, 3 permissions, 1 data type
Services
  • LLM Service
Permissions
  • filesystem:read
  • filesystem:write
  • shell:execute
Data Handling
  • source code
Security Passed
All checks passed v1.0.21 · scanner v3.3.0

Detected

  • Services: llm-service
  • Permissions:
  • Data Handling:
Version history 15 releases
v1.0.21 latest 17 July 2026

GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.

v1.0.20 3 July 2026

GH#745 — declare per-step `output: {name, type}` on every execution step (test_plan/text, tests/text, test_output/text, test_report/text, fix_verdict/decision). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.

v1.0.19 8 June 2026

GH#655 audit fix — rewrites `{{steps.Test Planning.output}}` → `{{steps.Plan Tests.output}}` in the workflow's `inputExpression` for the for-each loop. The `test-planning` slug was mirror-dropped to `plan-dev-tests` (title "Plan Tests") in Step 2; the Row 3b helper rewrote slug refs but missed display-name uses in this consumer. Engine validator would not have caught this (loop's inputExpression is runtime-substituted, not statically validated against priorTitles).

v1.0.18 7 June 2026

Fix-forward after Row 3b v1.0.17 publish failure. The v1.0.17 per-skrpt CI's "Register version with Hub API" step failed because the consumer's source `manifest.id` (b8e4f21a…) did not match the D1 catalogue row's id (41ed5303…) — a legacy drift from before Action 6 (`0bcc5ae0`) made publish-skrpt.mjs Step 2 INSERT use `manifest.id` for the D1 id column. v1.0.18 reconciles the source `manifest.id` to the catalogue authoritative value (Row-5-equivalent for consumers) and republishes. Per Adj-1: no re-tag of v1.0.17; the orphaned GitHub release artefact stays inert (no D1 versions row, no consumer pinned it).

v1.0.16 22 May 2026

Wave 2: re-signed with canonical engine signing pipeline.

v1.0.13 19 May 2026

Signature fix — RELEASE_NOTES.md now included in integrity checksum.

v1.0.12 19 May 2026

Initial catalogue release with full structural and content-quality validation. All scanner checks pass.

v1.0.11 18 May 2026

Release notes unavailable for this version.

v1.0.10 14 May 2026

Release notes unavailable for this version.

v1.0.9 14 May 2026

Release notes unavailable for this version.

v1.0.7 27 April 2026

Release notes unavailable for this version.

v1.0.6 25 April 2026

Release notes unavailable for this version.

v1.0.5 16 April 2026

Release notes unavailable for this version.

v1.0.3 13 April 2026

Release notes unavailable for this version.

v1.0.0 11 April 2026

Release notes unavailable for this version.

More from Developer

View all →

Send feedback

Sign in to send feedback — it lets us follow up and keeps the tracker free of spam.