Runs Azure Functions locally using Azure Functions Core Tools v4 (`func start`), Azurite storage emulation, and framework-native unit tests for handler code (.NET isolated worker model, Node.js v4, Python v2). Covers HTTP, queue, and timer trigger testing, admin-endpoint invocation for non-HTTP triggers, and binding verification via local.settings.json. Use when testing Azure Functions before deployment, reproducing trigger behaviour without live Azure services, or gating function handler logic in CI.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Azure Functions Core Tools v4 (func.exe) provides a local runtime that
mirrors the Functions host on Azure. Per
learn.microsoft.com/azure/azure-functions/functions-run-local,
func start starts all triggers in the project directory and outputs the
URL of every HTTP-triggered function. Azurite emulates Blob, Queue, and
Table Storage locally so queue and timer triggers can be exercised without
a live storage account.
Nearest neighbours and how this skill differs:
aws-sam-local-testing wraps SAM Local for Lambda/API Gateway
(its references/dotnet.md covers the .NET Lambda test runner). This
skill is Azure-only and covers func start, Azurite, the .NET
isolated worker model (Microsoft.Azure.Functions.Worker), and
admin-endpoint invocation.serverless-integration-test-builder builds multi-function integration
harnesses. This skill covers the per-function local invocation workflow.func --version shows 4.x) and Azurite, then
scaffold with func init and add triggers with func new - commands in
references/local-setup.md.AzureWebJobsStorage to UseDevelopmentStorage=true in
local.settings.json so queue and timer triggers route to Azurite; keep
the file git-ignored.func start from the project root and note the
printed HTTP trigger URLs.curl; fire non-HTTP (queue/timer) triggers
through the /admin/functions/<name> endpoint - see
references/triggering-functions.md.dotnet test / pytest / npm test into CI
using the workflow in references/triggering-functions.md.local.settings.json, Azurite, and func start:
references/local-setup.md.A .NET isolated function OrderProcessor is triggered by the orders
queue. To gate it locally before deploy:
func init OrderApp --worker-runtime dotnet-isolated, then
func new --template "Azure Queue Storage Trigger" --name OrderProcessor.
In local.settings.json, set
"AzureWebJobsStorage": "UseDevelopmentStorage=true".
Run azurite --silent --location ./azurite-data in one shell and
func start in another.
Fire the trigger through the admin endpoint:
curl --request POST -H "Content-Type: application/json" \
--data '{"input":"{\"orderId\":42}"}' \
http://localhost:7071/admin/functions/OrderProcessor
The host returns HTTP 202 (Accepted) and the function logs the processed order.
Unit-test OrderProcessor.Run with a mocked FunctionContext (xUnit),
asserting the parsed order id - no host required.
Result: queue-trigger wiring is verified against Azurite and handler logic is gated in CI, with no live Azure Storage account.
| Anti-pattern | Why it fails | Fix |
|---|---|---|
| Skip Azurite for queue/timer triggers | Queue and storage triggers require AzureWebJobsStorage; without it func start errors | Start Azurite and set "AzureWebJobsStorage": "UseDevelopmentStorage=true" in local.settings.json |
| Use in-process model for new projects | Support for in-process model ends 2026-11-10 per learn.microsoft.com/azure/azure-functions/dotnet-isolated-in-process-differences | Use --worker-runtime dotnet-isolated |
| Hard-code connection strings in code | Secrets leak to source control | Use local.settings.json Values array; it is git-ignored by default |
Call admin endpoint without Content-Type: application/json | Host rejects the request | Always include Content-Type: application/json header and {"input":"..."} body |
Commit local.settings.json | Contains secrets | Verify .gitignore excludes it; use func settings to sync with Azure app settings |
Use func host start for Core Tools v4 | Command removed in v4; it was v1.x syntax per Core Tools docs | Use func start |
func start. Test with connection strings locally; verify RBAC
in a staging environment.cold-start-budget-reference.func start:
learn.microsoft.com/azure/azure-functions/functions-run-localaws-sam-local-testing,
cold-start-budget-reference,
cloudflare-workers-miniflare,
serverless-integration-test-builder还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Builds a CI gate that fails the build on **new** WCAG / a11y violations introduced by a PR while grandfathering pre-existing violations on a per-rule / per-page baseline. Aggregates verdicts from axe-core / pa11y / Lighthouse a11y / WAVE / IBM Equal Access scans. Use when a project has accumulated a11y debt and a strict "zero violations" gate would block every PR - the ratchet pattern lets the team ship while preventing regressions.
中文简介正在准备中。当前显示原文说明。
Workflow skill that builds an A/B-test validity checklist from an experiment proposal, walking the canonical design-correctness gates - pre-registered OEC/power/guardrails, randomization unit + SRM check, assignment integrity, telemetry, peeking discipline, novelty/primacy, post-experiment SRM re-check - into a per-experiment checklist + sign-off form. Use when launching, auditing, or governing an experiment. For pitfall mechanics (guardrails, peeking) see experiment-results-interpreter's references; to read an already-valid result use experiment-results-interpreter; for per-SDK harness tests use experiment-sdk-testing - this gates DESIGN, not SDK code.
中文简介正在准备中。当前显示原文说明。
The single install-flow skill: the reference contract for the PWA install flow (installability gate fields, `beforeinstallprompt` handshake, per-platform paths - Android WebAPK / iOS Share menu / Firefox no-op - and the `display-mode` post-install signal, in references/install-flow-reference.md) plus the build-an-X workflow that emits the Add-to-Home-Screen suite. Walks the four-stage timeline, emitting one test per gate cell per [web.dev/articles/install-criteria][install-criteria], the deferred-prompt → `prompt()` → `userChoice` chain per [web.dev/articles/customize-install][customize-install], the iOS Safari manual-metadata branch (`apple-touch-icon`) per [web.dev/learn/pwa/installation][learn-pwa], and the post-install `(display-mode: standalone)` MQ assertion. Output: a Playwright spec with per-stage cells plus a coverage matrix. Use when a PWA's manifest, icons, or install handler change, when install conversion drops at an unknown stage, or when triaging a flaky install assertion.
中文简介正在准备中。当前显示原文说明。
Build-an-X workflow that uses an LLM to map existing tests to spec sections - given a spec doc + the test suite, the LLM identifies which tests cover which sections, surfaces uncovered sections (gap), and recommends specific tests to add. Output is a coverage matrix per spec ID. Scope is mapping tests that already exist and naming the gaps, not authoring tests for new acceptance criteria. Use when a spec doc and a test suite both exist but nobody can say which requirements are actually covered - before a release sign-off, an audit, or a decision about where to spend the next round of test effort.
中文简介正在准备中。当前显示原文说明。
Generates tests from natural-language specs (acceptance criteria, user stories, requirements) using an LLM, with confidence scoring per test case (LLM self-assessment plus heuristics: assertion quality, naming, completeness), batching uncertain cases for human review, and integration with the team's existing test framework. Use when the user asks to generate unit tests from acceptance criteria, convert user stories to test cases, automate test creation from requirements, or augment a spec-driven test suite with AI-generated stubs that are then curated before merge.
中文简介正在准备中。当前显示原文说明。
Configures Allure Report (test-runner adapter install, `allure-results` directory wiring, `categories.json` for failure classification, `history-trend.json` retention via the copy-history-between-runs pattern), runs the Allure CLI to convert `allure-results` to a static HTML site, and uploads the report as a CI artifact. Use when the team needs richer test reporting than JUnit XML - step-level attachments, per-test history, retry tracking, and severity / epic / feature labeling across framework-agnostic adapters (pytest, Jest, JUnit, TestNG, NUnit, Mocha). As a rich static HTML report generator, it is the open-source alternative to the sunset ExtentReports (JVM/.NET per-test HTML narrative); for hosted cross-run flakiness analytics rather than a static per-run report use currents-integration.
中文简介正在准备中。当前显示原文说明。