Token导航 LogoToken导航TokenDH.com
开发需要联网github未标认证来源可访问许可证需确认审计通过

frappe-testing冰沙测试

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

1,572

周安装

63

GitHub Stars

16

下载量

509
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:frappe-testing(冰沙测试)
来源仓库:https://github.com/lubusin/agent-skills
仓库路径:skills/frappe-testing
安装命令:
npx skills add https://github.com/lubusin/agent-skills --skill frappe-testing
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/lubusin/agent-skills --skill frappe-testing

简介

用于辅助测试设计、自动化测试、用例整理和回归验证。

  • 适合编写单元测试、端到端测试或根据日志定位问题。
  • 使用时需确认项目测试框架、运行命令和夹具数据。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。
  • 涉及浏览器或外部服务时应区分本地模拟与生产环境。
  • frappe-testing 属于开发类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Frappe Testing

Write and run tests for Frappe applications using the built-in testing framework.

When to use

  • Writing unit tests for DocType controllers
  • Writing integration tests for workflows and APIs
  • Running existing test suites
  • Debugging test failures
  • Setting up CI pipelines for Frappe apps

Inputs required

  • App name to test
  • Site name for test execution
  • Specific module/DocType to test (optional)
  • Test environment (dev site, dedicated test site)

Procedure

0) Setup test environment

# Install dev dependencies
bench setup requirements --dev

# Ensure site is ready
bench --site <site> migrate

1) Run tests

# Run all tests for an app
bench --site <site> run-tests --app my_app

# Run tests for specific module
bench --site <site> run-tests --module my_app.my_module.tests

# Run tests for specific DocType
bench --site <site> run-tests --doctype "My DocType"

# Verbose output
bench --site <site> run-tests --app my_app -v

# Run single test file
bench --site <site> run-tests --module my_app.doctype.sample_doc.test_sample_doc

2) Write DocType tests

Create test_<doctype_name>.py alongside the DocType:

# my_app/doctype/sample_doc/test_sample_doc.py
import frappe
from frappe.tests.utils import FrappeTestCase

class TestSampleDoc(FrappeTestCase):
    def setUp(self):
        # Create test data
        self.doc = frappe.get_doc({
            "doctype": "Sample Doc",
            "title": "Test Document"
        }).insert()

    def tearDown(self):
        # Cleanup
        frappe.delete_doc("Sample Doc", self.doc.name, force=True)

    def test_creation(self):
        self.assertEqual(self.doc.title, "Test Document")

    def test_validation(self):
        doc = frappe.get_doc({
            "doctype": "Sample Doc",
            "title": ""  # Invalid - required field
        })
        self.assertRaises(frappe.ValidationError, doc.insert)

    def test_workflow(self):
        self.doc.status = "Approved"
        self.doc.save()
        self.assertEqual(self.doc.status, "Approved")

3) Write API tests

# my_app/tests/test_api.py
import frappe
from frappe.tests.utils import FrappeTestCase

class TestAPI(FrappeTestCase):
    def test_whitelist_method(self):
        from my_app.api import process_order

        # Create test order
        order = frappe.get_doc({
            "doctype": "Sales Order",
            "customer": "_Test Customer"
        }).insert()

        # Test the API
        result = process_order(order.name, "approve")

        self.assertEqual(result["status"], "success")

        # Cleanup
        frappe.delete_doc("Sales Order", order.name, force=True)

    def test_permission_denied(self):
        # Test as restricted user
        frappe.set_user("guest@example.com")

        from my_app.api import sensitive_action
        self.assertRaises(frappe.PermissionError, sensitive_action, "doc-001")

        # Reset user
        frappe.set_user("Administrator")

4) Test permissions

def test_role_permissions(self):
    # Create user with specific role
    user = frappe.get_doc({
        "doctype": "User",
        "email": "test_user@example.com",
        "roles": [{"role": "Sales User"}]
    }).insert()

    frappe.set_user("test_user@example.com")

    # Test permission
    self.assertTrue(frappe.has_permission("Sales Order", "read"))
    self.assertFalse(frappe.has_permission("Sales Order", "delete"))

    # Cleanup
    frappe.set_user("Administrator")
    frappe.delete_doc("User", user.name, force=True)

5) Use fixtures

# my_app/doctype/sample_doc/test_records.json
[
    {
        "doctype": "Sample Doc",
        "title": "Test Record 1"
    },
    {
        "doctype": "Sample Doc",
        "title": "Test Record 2"
    }
]

Reference in tests:

class TestSampleDoc(FrappeTestCase):
    def test_fixture_loaded(self):
        doc = frappe.get_doc("Sample Doc", "Test Record 1")
        self.assertIsNotNone(doc)

6) Run UI tests (Cypress)

# Run UI tests for an app
bench --site <site> run-ui-tests my_app

# Headless mode
bench --site <site> run-ui-tests my_app --headless

Verification

  • All tests pass: bench --site <site> run-tests --app my_app
  • No test pollution (tests are isolated)
  • Tests run in < 5 minutes for fast feedback
  • CI pipeline runs tests on each commit

Failure modes / debugging

  • Test not found: Ensure filename starts with test_ and class/method names follow conventions
  • Database errors: Tests may not be isolated—check for missing cleanup
  • Permission errors in tests: Use frappe.set_user("Administrator") in setup
  • Slow tests: Avoid unnecessary fixtures, mock external services

Escalation

References

Guardrails

  • Use test fixtures: Load test data via fixtures, not manual creation in each test
  • Clean up test data: Delete created records in tearDown() or use frappe.db.rollback()
  • Mock external services: Never call real APIs in tests; mock HTTP calls
  • Isolate tests: Each test should be independent; no reliance on test execution order
  • Set user context explicitly: Use frappe.set_user() to test as specific users

Common Mistakes

MistakeWhy It FailsFix
Not using FrappeTestCaseMissing test setup/teardownExtend frappe.tests.utils.FrappeTestCase
Missing db rollbackTest pollution, flaky testsUse frappe.db.rollback() in tearDown or transactions
Flaky async testsIntermittent failuresUse frappe.tests.utils.run_until() or proper async handling
Testing implementation not behaviorBrittle testsTest outcomes, not internal method calls
Hardcoded test dataConflicts with existing dataUse unique names like _Test Record {uuid}
Skipping permission testsSecurity holesTest with different user roles, not just Administrator

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.37%
按下载量换算185

Claude

30.86%
按下载量换算157

Cursor

20%
按下载量换算102

Gemini CLI

9.31%
按下载量换算47

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills