frappe-ui-testing
Skill1 starsChanged 2 months agoNo licenceView on GitHub
Set up and write browser/UI/end-to-end tests for a custom Frappe or ERPNext app using Cypress via `bench run-ui-tests`, and wire them into GitHub Actions for a repo that already runs Python unit tests. Use this skill whenever a task involves: adding UI tests, E2E tests, browser tests, Cypress or `cypress.config.js` to a Frappe app; `bench --site X run-ui-tests <app>`; writing a `.cy.js` spec against the Frappe Desk; frappe's Cypress custom commands (`cy.login`, `cy.new_form`, `cy.fill_field`, `cy.fill_table_field`, `cy.call`, `cy.insert_doc`, `cy.click_action_button`); `@whitelist_for_tests` server-side fixtures for UI tests; a `ui-tests.yml` GitHub Actions workflow for a Frappe app; or sharding/parallelising Cypress across a CI matrix with `cypress-split`. Also covers how to structure a growing suite — the `cypress/` folder layout, form/transaction controller classes, reusing the app's `test_records.json` from a spec, and designing `ui_test_helpers.py` fixtures. Reach for it before creating any Cypress scaffolding in a Frappe app — `bench run-ui-tests` resolves the binary and the config from two different directories, and getting that wrong is the single most common way this setup fails.
- Reads credentials
- Deletes or force-pushes
- Installs packages
In this repository4 other files it gives its agents.
- code-simplificationSkill
- ewaybill-nic-rollout-patternSkill
- gst-isd-distributionSkill
- rag-in-erpSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.