Showing 39751–39780 of 77200 skills
Use whenever Ruby Sidekiq workers need tests: the fake!, inline! and disable! testing modes, RSpec and Minitest helpers, clearing jobs between tests, and assertions on enqueued jobs, arguments, scheduling, retries and unique jobs.
MaarkssDN/Birthub-360
Use when a QA manager needs to know what the team can do today versus what its projects demand, before quarterly planning, a training budget decision or opening a role. Builds an evidence-backed skill matrix, classifies and ranks gaps and recommends train, hire or bring in an expert per gap.
MaarkssDN/Birthub-360
Use when SLOs and an endpoint list exist but nobody has decided which load tests to run, what load each carries or what counts as failure. Turns each SLO into scenarios with a load profile, workload model, pass/fail threshold and error-budget allowance, before any tool is configured.
MaarkssDN/Birthub-360
Use when a team needs a fast per-deploy gate: a smoke suite of 5-15 critical journeys (login, checkout, payment, main read path) that runs in under 5 minutes as E2E or API tests and blocks the deploy when it fails, with retries for transient failures.
MaarkssDN/Birthub-360
Use when an SMS flow sent through Twilio needs tests: Twilio magic numbers and test credentials for safe runs, GSM-7 vs UCS-2 segment counts, rate limits, STOP and HELP opt-out keywords, and sender ID vs short code vs 10DLC differences.
MaarkssDN/Birthub-360
Use when preparing for a SOC 2 Type II audit or any audit that needs evidence packages from automated tests: per-criterion artifacts (CC1-CC9 and optional categories), collection from CI, audit and access logs and change records, Vanta, Drata or Secureframe formats, and observation-period sampling.
MaarkssDN/Birthub-360
Use when warehouse data quality (Snowflake, BigQuery, Postgres, Redshift and others) should be checked with YAML-based SodaCL: writing checks, configuration.yml data sources, soda scan runs and CI gating on the exit code, with Soda Core or Soda Cloud.
MaarkssDN/Birthub-360
Use when a team wants maintainability and technical-debt ratings to gate PRs, or a SonarQube project reports numbers nobody tied to a gate. Runs SonarQube or SonarCloud on production code for code smells, bugs and maintainability ratings, the maintainability view rather than security.
MaarkssDN/Birthub-360
Use when a team runs SonarQube or SonarCloud for multi-language static analysis and code quality: sonar-scanner and sonar-project.properties, Sonar Way profiles and custom rules, quality gates on new code, branch and PR analysis, and NOSONAR or SuppressWarnings suppressions.
MaarkssDN/Birthub-360
Use when a user story, acceptance criterion, PRD section, API contract or PR description is about to go to implementation and someone needs to know which sentences can't be verified. Scores each claim as observable, decidable and bounded, rewrites weak ones and gives a BLOCK, REVIEW or OK verdict.
MaarkssDN/Birthub-360
Detecção e eliminação de problemas de N+1 queries no Prisma Client e rotas do backend. Otimiza carregamento de relacionamentos reais do schema (Lead, Activity, Contact, Company) e reduz latência no PostgreSQL.
MaarkssDN/Birthub-360
Use whenever code that sends or receives AWS SQS messages needs tests: Standard vs FIFO semantics, visibility timeouts, dead-letter queues for poison messages and retention, using LocalStack, aws-sdk-client-mock for TypeScript or moto for Python.
MaarkssDN/Birthub-360
Use when a repo already has Storybook and wants a visual test per story: the hosted Chromatic addon, or the self-hosted Storybook test-runner with a postVisit hook calling Playwright's toHaveScreenshot, plus CI setup.
MaarkssDN/Birthub-360
Use when a design, story or architecture sketch touching login, user data, payments, file uploads or an external integration is about to be built with no threat model. Walks assets and trust boundaries through Microsoft's STRIDE categories, triages threats and writes the threat model into the repo.
MaarkssDN/Birthub-360
Use when Stripe subscriptions or recurring billing need tests: trial to paid, proration on upgrade and downgrade, dunning on failed renewals, cancel and reactivate, and the subscription webhook events, using Stripe test clocks to skip through billing cycles without waiting.
MaarkssDN/Birthub-360
Use whenever code that takes payments with Stripe needs tests: test-mode keys, test cards for success, declines and 3D Secure, stripe listen to forward webhooks locally, stripe trigger fixtures, and Stripe-Signature verification.
MaarkssDN/Birthub-360
Use when a JavaScript or TypeScript suite has high coverage but bugs still slip through, and the team wants mutation testing to find weak tests. Sets up StrykerJS: the Jest, Vitest, Mocha or Karma runner, stryker.conf.json, thresholds and incremental runs on pull requests.
MaarkssDN/Birthub-360
Use when a .NET (C#) test suite needs mutation testing to show whether the tests catch bugs. Sets up Stryker.NET: the dotnet-stryker tool, project scoping, xUnit, NUnit or MSTest, stryker-config.json thresholds and CI runs.
MaarkssDN/Birthub-360
Use when testing FHIR servers, EHR integrations, claims processing or other health IT needs realistic patient records with no HIPAA exposure. Runs MITRE Synthea to simulate patient populations and outputs FHIR R4, STU3, DSTU2, C-CDA or CSV, with custom disease modules.
MaarkssDN/Birthub-360
Use whenever someone asks for test factories or a FactoryBot setup, even a quick one: factories with traits and associations (Ruby, Rails), Mimesis bulk data (Python), Bogus Faker<T> builders (.NET), or which generator fits. Same fixture in each tool; plain fake values stay with faker-data.
MaarkssDN/Birthub-360
Use when a critical user journey needs continuous checks in production, or monitor coverage was never derived from real usage. Writes a synthetic monitor for Datadog, Pingdom, Checkly or New Relic with browser or API steps, cadence, checks and alerts, and ranks unmonitored journeys from RUM data.
MaarkssDN/Birthub-360
Use when seeding non-production environments, building demo data, or replacing real personal data in copied datasets. Generates fake but valid-looking PII: names, emails, phones, addresses, national IDs and SSNs, Luhn-valid test card numbers and birth dates, never real people's data.
MaarkssDN/Birthub-360
Use when managing test cases in TestRail, Xray, Zephyr Scale, Allure TestOps or Qase: writing cases from a spec, organizing suites, steps with expected results, linking requirements, bulk importing from CSV or JSON, migrating between tools or mass edits. Pushing run results is test-management-sync.
MaarkssDN/Birthub-360
Use when a tenant onboarding or offboarding flow is added or changed, or before a compliance review: tests for account creation, isolation from the first API call, default quotas, billing links, seed data, idempotent re-provisioning and full deletion on teardown.
MaarkssDN/Birthub-360
Use when a feature has no story, acceptance criteria or docs, only a running app, recording, screenshot or verbal brief, and it needs test cases. Explores the feature and applies HTSM/SFDPOT, Whittaker attacks, FEW HICCUPPS oracles and ISO 25010 to produce a test case matrix.
MaarkssDN/Birthub-360
Pure-reference catalog of test-code conventions: AAA structure (Arrange / Act / Assert), per-test single-responsibility, descriptive naming (`{sut}_{scenario}_{expected}`), assertion specificity, mocking rationale (state vs behavior, fake vs mock), fixture-coupling rules, the magic-number / hard-coded-string anti-patterns, and step design (§11: FIRST principles, step granularity, the mechanical → page → business abstraction layers, the rule-of-three extraction heuristic, declarative phrasing); the E2E selector-priority, web-first-assertion, and step-grouping conventions live in references/. Use as the shared rule book a test-code review cites back to, or as onboarding for what makes a test code-reviewable; to score a test's quality on weighted axes use test-design-scorecard, and for setup/teardown isolation specifically use test-isolation-patterns.
MaarkssDN/Birthub-360
Use when a team can write only a handful of new tests and must pick which uncovered code matters most, or when some modules lose coverage while the total looks fine. Ranks uncovered branches in the diff by complexity, churn and test cost, and tracks per-file coverage drift.
MaarkssDN/Birthub-360
Use when choosing how a test suite builds its test data, or when fixtures have drifted into shared mutable state. Explains Test Data Builder, Factory, Object Mother, fixture composition, snapshots and production-data anonymization, and when each fits, before picking a tool.
MaarkssDN/Birthub-360
Use when a test diff needs a graded coaching review rather than a merge verdict: onboarding a new engineer, ramping up test discipline, or a quarterly per-author trend. Scores tests 1-5 on six design axes with explicit anchors and writes growth-framed feedback.
MaarkssDN/Birthub-360
Use when an epic or release is split into testable areas and someone must commit test capacity. Produces a PERT three-point estimate as ranges, with a named assumptions ledger and a split across developer, automation and exploratory work; also classifies a change set's shape from git history.
MaarkssDN/Birthub-360