Skip to content
cccskills
FreePublished on GitHub

azure-functions-tests

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.

The English summary is being prepared. Showing the original description.

testland/qa13 stars(GitHub 13 + cccskills 0)
Works withAWSAzure

Run score Not tested

See how to install

Files included (5)

  • SKILL.md8.2 KB
  • .tessl-plugin/plugin.json643 B
  • references/local-setup.md3.1 KB
  • references/triggering-functions.md1.9 KB
  • references/unit-testing-handlers.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

azure-functions-tests

Overview

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.

When to use

  • Local unit + integration tests for Azure Function handlers before deploy.
  • Reproducing HTTP, queue, or timer trigger behaviour without deploying.
  • CI gating on function handler logic in .NET, Node.js, or Python.
  • Verifying binding configuration with Azurite instead of live Azure Storage.

How to use

  1. Install Core Tools v4 (func --version shows 4.x) and Azurite, then scaffold with func init and add triggers with func new - commands in references/local-setup.md.
  2. Set AzureWebJobsStorage to UseDevelopmentStorage=true in local.settings.json so queue and timer triggers route to Azurite; keep the file git-ignored.
  3. Start Azurite, then run func start from the project root and note the printed HTTP trigger URLs.
  4. Exercise HTTP triggers with curl; fire non-HTTP (queue/timer) triggers through the /admin/functions/<name> endpoint - see references/triggering-functions.md.
  5. Unit-test handler logic directly (no running host) with the per-language patterns in references/unit-testing-handlers.md.
  6. Wire Core Tools + Azurite + dotnet test / pytest / npm test into CI using the workflow in references/triggering-functions.md.
  7. Confirm binding config against Azurite; verify Managed Identity / RBAC in a staging environment (see Limitations).

Reference files

Worked example

A .NET isolated function OrderProcessor is triggered by the orders queue. To gate it locally before deploy:

  1. func init OrderApp --worker-runtime dotnet-isolated, then func new --template "Azure Queue Storage Trigger" --name OrderProcessor.

  2. In local.settings.json, set "AzureWebJobsStorage": "UseDevelopmentStorage=true".

  3. Run azurite --silent --location ./azurite-data in one shell and func start in another.

  4. 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.

  5. 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-patterns

Anti-patternWhy it failsFix
Skip Azurite for queue/timer triggersQueue and storage triggers require AzureWebJobsStorage; without it func start errorsStart Azurite and set "AzureWebJobsStorage": "UseDevelopmentStorage=true" in local.settings.json
Use in-process model for new projectsSupport for in-process model ends 2026-11-10 per learn.microsoft.com/azure/azure-functions/dotnet-isolated-in-process-differencesUse --worker-runtime dotnet-isolated
Hard-code connection strings in codeSecrets leak to source controlUse local.settings.json Values array; it is git-ignored by default
Call admin endpoint without Content-Type: application/jsonHost rejects the requestAlways include Content-Type: application/json header and {"input":"..."} body
Commit local.settings.jsonContains secretsVerify .gitignore excludes it; use func settings to sync with Azure app settings
Use func host start for Core Tools v4Command removed in v4; it was v1.x syntax per Core Tools docsUse func start

Limitations

  • Azurite does not emulate Azure Files or Azure Data Lake Storage Gen2, per learn.microsoft.com/azure/storage/common/storage-use-azurite. Functions that use these services must connect to live Azure Storage during local testing.
  • Event Grid triggers require extra configuration to run locally; the admin-endpoint approach does not cover them. See learn.microsoft.com/azure/azure-functions/functions-run-local#run-a-local-function for the viewer web app approach.
  • Managed Identity authentication and RBAC roles cannot be replicated by func start. Test with connection strings locally; verify RBAC in a staging environment.
  • Cold-start behaviour differs from production. For cold-start budgets see cold-start-budget-reference.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a11y-violation-gate

Free

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.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

ab-test-validity-checklist

Free

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 English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

add-to-homescreen-flow-tests

Free

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.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

ai-spec-coverage-mapper

Free

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.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

ai-test-generator

Free

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.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

allure-reports

Free

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.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

See all skills by testland

Report a problem with this skill