Showing 39781–39810 of 77205 skills
Use when a complex stateful flow (checkout, onboarding, multi-step wizard) needs systematic model-based coverage that ad-hoc tests miss. Builds a state-machine model, checks it is complete, picks a coverage criterion, generates covering paths and turns them into a curated test suite.
MaarkssDN/Birthub-360
Use when a retrained ML model is a candidate for promotion and CI must block it if it got worse. Compares held-out accuracy, F1, AUC or RMSE with the production model within a tolerance, and checks key segments with Deepchecks so a global gain cannot hide a slice regression.
MaarkssDN/Birthub-360
Use when an ML model release is up for promotion and someone must decide which fairness and explainability evidence is required, or check the evidence against the model's risk tier. Assigns a low, medium or high tier, lists required artifacts and returns promote, needs-work or block.
MaarkssDN/Birthub-360
Use when a product speaks MQTT, STOMP or AMQP and its delivery guarantees need broker-backed tests: QoS 0, 1 and 2, retained messages, Last Will, shared subscriptions and $SYS with Mosquitto and paho-mqtt; STOMP and RabbitMQ AMQP tests via Testcontainers are in its references.
MaarkssDN/Birthub-360
Authors Mock Service Worker (MSW) request handlers for both browser and Node.js test environments using the `http.get` / `http.post` / `HttpResponse.json` API, wires them via `setupWorker` (browser) or `setupServer` (Node), and manages the test lifecycle (`server.listen` / `resetHandlers` / `close`). Use when the project uses JavaScript / TypeScript and needs to mock fetch / XHR at the network layer for both Vitest / Jest unit tests and Cypress / Playwright integration tests.
MaarkssDN/Birthub-360
Use when a C or C++ project built with Clang needs mutation testing. Sets up Mull: the version-matched package, -fpass-plugin build flags, mull-runner, mutators, path filters and GitHub Actions. Other languages: stryker-mutation, stryker-net-mutation, pitest-mutation, mutmut-mutation.
MaarkssDN/Birthub-360
Use when several security scanners (SAST, DAST, secrets, SCA, container, IaC) produce separate reports and the team needs one BLOCK or PASS. Normalizes and dedupes findings, records which scanners agree, rejects waivers without expiry or approver, adds EPSS and KEV, and writes one PR comment.
MaarkssDN/Birthub-360
Use before a multiplayer game goes to platform cert, where broken multiplayer is a common rejection. Builds a coverage matrix for connect, authority handoff, disconnect, reconnect and host migration under latency, loss and reordering for Unity Netcode, Unreal and Mirror, with a go/no-go gate.
MaarkssDN/Birthub-360
Use when a mutation testing run (StrykerJS, PIT, mutmut or Mull) has finished and surviving mutants need explaining. Classifies each survivor (missing case, weak assertion, equivalent, unreachable, flaky) and drafts the test that would kill it, without rewriting tests automatically.
MaarkssDN/Birthub-360
Use when a Python pytest or unittest suite needs mutation testing to show whether the tests catch bugs. Sets up mutmut: mutmut run, results and browse, applying survivors, pragma: no mutate suppressions and pyproject.toml config.
MaarkssDN/Birthub-360
Use when two concurrent database transactions can touch the same rows (balance debits, seat bookings, stock counts), or before changing a default isolation level. Tests which anomalies each level prevents (dirty, non-repeatable and phantom reads, write skew) in PostgreSQL, MySQL and SQL Server.
MaarkssDN/Birthub-360
Use when a PRD, design doc or product brief must be turned into testable non-functional requirements. Extracts performance, accessibility, security, i18n, reliability and observability needs as threshold-bound assertions, each mapped to its measurement source (Lighthouse, axe, OWASP ASVS, WCAG).
MaarkssDN/Birthub-360
Use when Jupyter notebooks must run in CI as tests, their outputs must stay stable, or a PR adding notebooks needs review. Wires papermill parameterized runs, nbval output checks, testbook unit tests, nbstripout and artifacts into GitHub Actions, plus a review checklist with a BLOCK or PASS verdict.
MaarkssDN/Birthub-360
Use when a team runs ProjectDiscovery Nuclei for template-based web scanning, alongside or beyond ZAP: choosing templates by path, tag or severity, rate limits, JSONL output, custom YAML matchers for app-specific checks, community CVE templates and CI severity gates.
MaarkssDN/Birthub-360
Use whenever an OAuth 2.0 or OpenID Connect client or resource server needs tests, whatever the identity provider: auth code with PKCE, client credentials, refresh-token rotation and reuse detection, state and nonce checks, scopes and strict redirect-URI matching, per the RFCs.
MaarkssDN/Birthub-360
Use when designing, reviewing or migrating a test framework's object model: Page Object, Screenplay, Component Object, App Actions, Service Object, Repository and Screen Object for desktop and mobile. Explains what each pattern is, when it fits, mixes to avoid, with citations and examples.
MaarkssDN/Birthub-360
Use when choosing or changing how a PWA route behaves offline, or a 'doesn't work offline' bug needs pinning to a route. Maps each route to an offline caching recipe (cache first, network first and others), tests it with Playwright, and covers Workbox offlineFallback and storage choices.
MaarkssDN/Birthub-360
Use when an app uses Okta as its identity provider and needs tests for org config, sign-in policies or Identity Engine flows: per-PR or shared orgs, MFA enforcement, factor enrollment, recovery, SCIM provisioning and least-privilege API tokens.
MaarkssDN/Birthub-360
Use when a pull request or release changes an OpenAPI spec and breaking changes must be caught: removed endpoints, deleted schemas, narrowed enums, changed responses. Runs oasdiff breaking, grades findings ERR, WARN or INFO and gates CI with --fail-on.
MaarkssDN/Birthub-360
Governança de contratos de API no Birth Hub 360 (docs/openapi.yaml, Schemathesis e validação Zod). Garante que schemas do backend, tipos do frontend e especificações OpenAPI estejam perfeitamente sincronizados sem drift.
MaarkssDN/Birthub-360
Use whenever code that reads feature flags through OpenFeature, Unleash, Flagsmith or GrowthBook needs tests: InMemoryProvider for hermetic tests, evaluation details, hooks and targeting context in TypeScript, Java and Python, plus a flag test-matrix workflow. LaunchDarkly has launchdarkly-testing.
MaarkssDN/Birthub-360
Use when a service is instrumented with OpenTelemetry and alerts, SLOs or dashboards depend on span names or attributes a refactor could drop. Captures spans with the in-memory exporter in tests (Python, JS, Java) and asserts on names, attributes, status, kind and structure.
MaarkssDN/Birthub-360
Use when an OpenTelemetry Collector config changes (a new receiver, processor or exporter) and must be verified before deploy. Runs otelcol validate, uses the debug or file exporter to assert spans flow through the pipeline, and wires the check into CI.
MaarkssDN/Birthub-360
Use when adding or changing a transactional outbox, its relay or poller, or auditing it: tests that the DB write and event insert are atomic, events publish at least once in order, consumers dedupe and stay idempotent, and the relay recovers from failures.
MaarkssDN/Birthub-360
Use whenever two services (a frontend and an API, or two microservices) keep breaking each other's API: set up Pact consumer-driven contract tests, publish pacts to a broker, verify the provider and gate deploys with can-i-deploy.
MaarkssDN/Birthub-360
Use when a function or endpoint takes 3 or more inputs whose combinations matter and the full Cartesian product is too large. Combines boundary values, equivalence classes and pairwise (or N-wise) reduction into parameterized cases in the project's runner format.
MaarkssDN/Birthub-360
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