Showing 39691–39720 of 77203 skills
Use when a payment integration needs refund, dispute or payment-webhook tests: a refund matrix (full, partial, over-refund) for Stripe, Adyen, PayPal and Braintree, chargebacks with card-network reason codes, and webhook replay through each gateway's simulator.
MaarkssDN/Birthub-360
Use when code integrated with Adyen, PayPal or Braintree needs tests in sandbox mode: test credentials, sandbox URLs, deterministic test card numbers and each gateway's webhook simulator. For Stripe use stripe-test-cards-and-webhooks or stripe-subscription-billing-test-author.
MaarkssDN/Birthub-360
Use whenever tests must prove payment card handling meets PCI DSS v4.0: no stored or logged CVV, full card number (PAN), track data or PIN, card data only over strong TLS, cardholder data environment boundaries and segmentation, key management, SAQ level, scope reduction with hosted fields.
MaarkssDN/Birthub-360
Use when customer-facing PDFs must meet PDF/UA (Section 508, EU accessibility rules, public tenders) and each file must be proven tagged before release. Checks structure tags, alt text, reading order, language and title with veraPDF, PAC or similar, mapped to WCAG PDF techniques.
MaarkssDN/Birthub-360
Use when generated PDFs (invoices, contracts, regulatory filings) must not shift layout, or a template, font or PDF library is changing. Renders pages to images and pixel-diffs them against approved baselines, strips volatile metadata, and compares HTML-to-PDF engines.
MaarkssDN/Birthub-360
Use when visual regression tests run on BrowserStack Percy: @percy/cli with the Playwright, Cypress, Selenium or Storybook SDK, percy exec, viewports, masks and ignored regions, and reviewing diffs in Percy builds.
MaarkssDN/Birthub-360
Use when a deploy should be blocked by performance regressions from several tools. Combines k6, JMeter, Gatling or Locust results with Lighthouse CI Web Vitals, applies severity-aware thresholds against the main-branch baseline and returns one go/no-go with per-metric deltas.
MaarkssDN/Birthub-360
Use when the code under test is a PowerShell script, function, cmdlet or CLI run from pwsh. Sets up Pester v5: Describe/Context/It blocks, Should assertions, Mock, setup hooks, tags, code coverage and NUnit/JUnit XML output for CI.
MaarkssDN/Birthub-360
Use when non-production environments need masked production data. Classifies each field against GDPR, CCPA, NIST and HIPAA PII categories, picks a masking operator, decides pseudonymization vs anonymization, emits a Presidio, Faker and Synthea config and blocks promotion if a re-scan finds PII.
MaarkssDN/Birthub-360
Use when a Java or Kotlin test suite needs mutation testing. Sets up PIT (PITest) with the Maven or Gradle plugin: target classes and tests, mutation and coverage thresholds, mvn pitest:mutationCoverage and the HTML and XML reports.
MaarkssDN/Birthub-360
Use when a coding agent works with Playwright through playwright-cli, Playwright MCP or the planner, generator and healer Test Agents: setting them up, reviewing healer diffs before merging, debugging a failing test from its trace in a terminal with no display, and leaving a video receipt.
MaarkssDN/Birthub-360
Use when writing or debugging Playwright tests for a Chromium browser extension: the persistent-context fixture that loads the extension and finds its ID, why an edit seems to have no effect (reload matrix), and popup, content-script, storage and MV3 service-worker tests.
MaarkssDN/Birthub-360
Use when a Playwright suite has copy-pasted beforeEach setup that should be a fixture, or needs shared login, database or feature-flag setup across many specs. Builds test.extend fixtures with the right test or worker scope, setup and teardown, and per-worker isolation.
MaarkssDN/Birthub-360
Use when a project wants self-hosted visual regression tests in Playwright with no external service: toHaveScreenshot assertions, masks, clips and thresholds, per-OS and per-browser snapshot folders, --update-snapshots, and a viewport matrix across responsive breakpoints.
MaarkssDN/Birthub-360
Use whenever the task is to write, fix or speed up Playwright tests, even one quick test or a flaky one: role-based locators, web-first assertions instead of waitForTimeout, page objects, config and browser projects, traces, sharding and CI. Has the anti-pattern table for flaky Playwright tests.
MaarkssDN/Birthub-360
Use when a team needs custom policies that off-the-shelf scanners don't cover (cost limits, required tags, security baselines) enforced in CI. Writes OPA Rego policies and runs Conftest against Kubernetes manifests, Terraform plans, Dockerfiles or any structured data; also covers Cedar.
MaarkssDN/Birthub-360
Use after any user-visible incident to write a blameless post-mortem: a sourced timeline, root cause (what and why, not who), impact on users, revenue and SLOs, action items with owners, dates and success criteria, and what went well.
MaarkssDN/Birthub-360
Repairs Postman and Newman runs in CI - a reporter that never writes the HTML file the pipeline expects, a nightly job that fires requests as fast as it can until a partner API rate-limits it, or a report with one row per request when the collection asserts a dozen things between them. Authors Postman collections (requests, tests, variables, environments), runs them headless via the Newman CLI, configures reporters (cli / json / junit / html) for CI artifact upload, and drives data-driven runs from JSON / CSV iteration files. Use when HTTP API tests are authored in Postman and need to run, pace themselves, and report correctly in CI.
MaarkssDN/Birthub-360
Use when existing data (datasets, logs, free text) must be scanned for personal data or redacted: Microsoft Presidio analyzer and anonymizer, built-in recognizers for names, emails, cards, SSNs, IBANs and national IDs, custom pattern recognizers, score thresholds and CI gates.
MaarkssDN/Birthub-360
Use when an app has a Print button or print stylesheet that is untested, or printed and PDF copies break in the wrong places. Tests print CSS with Playwright print emulation and page.pdf(): @page size and margins, page breaks, orphans and widows, and print-only rules.
MaarkssDN/Birthub-360
Use when a canary deploy needs an automatic promote or rollback decision instead of someone watching dashboards. Compares the canary's error rate, p50, p95 and p99 latency and business KPIs with the baseline over the observation window, with absolute and relative thresholds and a significance check.
MaarkssDN/Birthub-360
Use when LLM prompts or RAG pipelines need eval-driven regression tests with Promptfoo: promptfooconfig.yaml providers, prompts and tests, deterministic, semantic, model-graded, latency and cost assertions, promptfoo eval and view, and CI gating.
MaarkssDN/Birthub-360
Use when a Rust project needs property-based tests, especially for parsers, serializers and functions with structured input. Sets up proptest: the proptest! macro, strategies for collections, regex strings and any, shrinking and the persisted regression file.
MaarkssDN/Birthub-360
Use when a pull request changes .proto files for gRPC services, Buf Schema Registry modules or message-bus payloads, and consumers must not break. Runs buf breaking against a past version, picks the FILE, PACKAGE, WIRE_JSON or WIRE category, sets exemptions and gates CI.
MaarkssDN/Birthub-360
Use when preparing an app for translation, checking localization infrastructure, or when pseudo-localization comes up. Replaces strings with accented, 35%-longer variants to expose hardcoded text, truncation, encoding and bidi problems without real translators.
MaarkssDN/Birthub-360
Configures and runs async Python tests with pytest-asyncio: installs the plugin, selects asyncio_mode (auto vs strict), scopes event loops (function/class/module/session), writes async fixtures with @pytest_asyncio.fixture, mocks coroutines with AsyncMock, and tests FastAPI (httpx.AsyncClient + ASGITransport) and aiohttp (aiohttp_client fixture) applications. Use when a Python project contains async def test_ functions, FastAPI/aiohttp endpoints, or any asyncio-based code that needs pytest integration. Do NOT use for general pytest fixture design, parametrize patterns, or conftest.py structure without an asyncio-specific problem (event-loop scoping, mode config, AsyncMock, ASGI client): use python-unit-tests for those.
MaarkssDN/Birthub-360
Use whenever the task is to write, add, fix or review Python tests, even quick pytest tests for a single function: edge cases, fixtures and conftest.py, parametrize tables, mocking, markers, coverage gates and CI. Has the pytest checklist for edge cases and weak assertions.
MaarkssDN/Birthub-360
Use when embedded tests must run on a virtual MCU or SoC instead of the host or real hardware, for correct endianness, alignment and interrupts: qemu-system-arm, aarch64 and riscv32 machine and CPU flags, loading ELF binaries, semihosting exit codes, GDB and QMP, and CI.
MaarkssDN/Birthub-360
Use whenever Qt C++ code needs unit or GUI tests in-process: Qt Test entry macros, private-slot test functions, QVERIFY, QCOMPARE and data-driven QFETCH, simulated mouse, key and touch events, QSignalSpy, QBENCHMARK and JUnit XML output for CI, including Qt Quick and QML logic.
MaarkssDN/Birthub-360
Use when a weekly quality review, sprint check-in or quarterly portfolio review is due and the numbers already exist in CI, the tracker and the quarantine list. Computes pass rate, escaped defects and flake debt, rates each area red, amber or green, and rolls teams up into a portfolio view.
MaarkssDN/Birthub-360