원클릭으로 Manus에서 모든 스킬 실행

koha-cypress

스타2

포크0

업데이트2026년 6월 8일 13:47

Run Koha Cypress end-to-end tests. Cypress runs from the HOST (not the KTD container) — KTD exposes the staff/OPAC interfaces on localhost and Cypress drives a real browser. Pass a spec path or directory under t/cypress/integration/.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

mrenvoize

mrenvoize/koha-contributor

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Critical: Cypress runs from HOST, not container

KTD already exposes the web UI on localhost. Cypress on the host drives a real browser against that. Running Cypress inside the container also works but is slower and harder to debug — only fall back to it if Node/npx isn't available on the host.

Steps

Verify KTD is up and the staff interface responds:
```
curl -sf -o /dev/null http://localhost:8081/ && echo OK || echo "KTD not responding on :8081"
```
If that fails, tell the user to start KTD (ktd up) and stop.
Normalise the spec path. Strip any leading absolute path so it's repo-relative (e.g. t/cypress/integration/Biblio/bookingsModal_spec.ts).

Run Cypress headlessly from the host (Koha repo root):

npx cypress run --spec "<path>"

For a whole directory:

npx cypress run --spec "t/cypress/integration/Acquisitions/"

Container fallback (only if host Cypress fails):

ktd --name "${KTD_INSTANCE:-kohadev}" --shell --run 'yarn cypress run --spec <path>'

Narrowing during development

To run a single test within a spec, ask the user if they want .only added to the source temporarily:

it.only("only run this one", () => { ... });
it("not this one", () => { ... });

Use it.skip(...) to skip. Remind the user to remove .only/.skip before committing — they will fail QA / leave dead tests.

Common failures

Cypress could not verify…has not exited cleanly — KTD is up but the app errored on load. Hit the URL in a browser to see the actual error; fix the underlying app issue, not the Cypress invocation.
Failed to connect to localhost — KTD is down or on a different port. Check docker ps for the actual port mapping (default 8081 staff, 8080 OPAC).
Authentication tests failing locally but passing in CI — Koha test database fixtures may be stale; run ktd --restart or rebuild KTD.

Output

Report pass/fail counts and the failing spec(s). For failures, include the first error stack from the Cypress output — the user usually doesn't need the full screenshot path.

이 저장소의 다른 Skills

같은 저장소

koha-bz

mrenvoize/koha-contributor

File a Koha bug on bugs.koha-community.org and attach commits non-interactively via git bz. Use when the user wants to submit a patch, file a bug, or open a bz/Bugzilla ticket for Koha. Arguments (optional, free-form): summary or component hints. Without args, derive details from the current branch and HEAD commits.

2026-06-162

koha-build

mrenvoize/koha-contributor

Build Koha frontend assets (CSS, JS, OpenAPI spec) inside the KTD container. Use after editing SCSS, Vue components, or api/v1/swagger/*.yaml. After swagger changes you must also run restart_all to reload services — yarn build alone is not enough.

2026-06-082

koha-prove

mrenvoize/koha-contributor

Run Koha Perl tests inside the KTD container. Pass a test file or directory path (relative to the Koha repo root, or absolute). Handles both t/ and t/db_dependent/ automatically.

2026-06-082

koha-qa

mrenvoize/koha-contributor

Run the Koha QA script (koha-qa.pl) inside KTD before submitting patches. Surfaces critic, POD, file_permissions, tinyint_has_boolean_flag, and other QA failures the community reviewers will check. Run after every commit; fix flagged issues before pushing.

2026-06-082

koha-schema-apply

mrenvoize/koha-contributor

Apply a Koha DB schema change end-to-end after editing kohastructure.sql and the atomicupdate file. Runs updatedatabase.pl in KTD, regenerates DBIC schema with dbic --force, and reminds about the manual is_boolean / relationship edits below the marker line. Use this after the atomicupdate skill has scaffolded the file and the SQL is filled in.

2026-06-082

koha-review

mrenvoize/koha-contributor

QA review a Koha patchset for regressions, security, code quality, and Koha-specific conventions. Use when the user says "QA this", "review this patchset/branch/PR", "review my work", or "review N commits". Auto-detects patchset scope, runs specialist review agents in parallel based on file types touched, and synthesises findings into Critical/Important/Suggestion buckets with file:line citations.

2026-05-082

name	koha-cypress
description	Run Koha Cypress end-to-end tests. Cypress runs from the HOST (not the KTD container) — KTD exposes the staff/OPAC interfaces on localhost and Cypress drives a real browser. Pass a spec path or directory under t/cypress/integration/.

Run Cypress E2E tests against KTD.

Arguments: $ARGUMENTS

Critical: Cypress runs from HOST, not container

Steps

Verify KTD is up and the staff interface responds:
```
curl -sf -o /dev/null http://localhost:8081/ && echo OK || echo "KTD not responding on :8081"
```
If that fails, tell the user to start KTD (ktd up) and stop.
Normalise the spec path. Strip any leading absolute path so it's repo-relative (e.g. t/cypress/integration/Biblio/bookingsModal_spec.ts).

Run Cypress headlessly from the host (Koha repo root):

npx cypress run --spec "<path>"

For a whole directory:

npx cypress run --spec "t/cypress/integration/Acquisitions/"

Container fallback (only if host Cypress fails):

ktd --name "${KTD_INSTANCE:-kohadev}" --shell --run 'yarn cypress run --spec <path>'

Narrowing during development

To run a single test within a spec, ask the user if they want .only added to the source temporarily:

it.only("only run this one", () => { ... });
it("not this one", () => { ... });

Use it.skip(...) to skip. Remind the user to remove .only/.skip before committing — they will fail QA / leave dead tests.

Common failures

Cypress could not verify…has not exited cleanly — KTD is up but the app errored on load. Hit the URL in a browser to see the actual error; fix the underlying app issue, not the Cypress invocation.
Failed to connect to localhost — KTD is down or on a different port. Check docker ps for the actual port mapping (default 8081 staff, 8080 OPAC).
Authentication tests failing locally but passing in CI — Koha test database fixtures may be stale; run ktd --restart or rebuild KTD.

Output

Report pass/fail counts and the failing spec(s). For failures, include the first error stack from the Cypress output — the user usually doesn't need the full screenshot path.