Testing
OAuth2 testing requires either a real OAuth provider in test mode or a mock OAuth server for unit and integration tests. The authorization code flow involves browser redirects that are hard to automate — mock servers eliminate the browser redirect while still testing your token exchange and validation logic. This guide
Testing
Salesforce requires a minimum of 75% Apex code coverage before any deployment to production. This guide covers writing Apex unit tests, mocking callouts and DML, testing flows, and automating UI tests with Provar inside a CI pipeline. Why Salesforce Testing Is Different Testing Salesforce applications comes with unique constraints that
Testing
DeepEval brings unit testing discipline to LLM applications. Write assertions on model outputs the same way you write pytest assertions on function return values — with G-Eval metrics, faithfulness checks, and hallucination detection. This tutorial walks you from installation to CI-integrated test suite. Why LLM Applications Need Unit Tests
Testing
Auth0 testing requires a dedicated test tenant, programmatic token generation for API tests, mock JWKS servers for unit tests, and cypress-auth0 or Playwright helpers for E2E tests. Testing against your production Auth0 tenant pollutes logs and risks rate limits. This guide covers the right setup for each test layer.
Testing
dbt ships with four built-in tests (not_null, unique, accepted_values, relationships) that cover the basics. For richer assertions—value ranges, regex patterns, statistical checks—add the dbt-expectations package. When neither covers your case, write a custom generic test. This guide covers all three layers plus how to
Testing
PCI DSS compliance testing is about verifying that cardholder data is handled securely — not stored when it shouldn't be, encrypted when transmitted, and accessible only to authorized systems. Most developers don't need to handle raw card data at all if they use Stripe or Braintree'
Testing
Payment API calls in unit tests create slow, flaky tests with real rate limits and network dependencies. The solution is mocking at the HTTP layer — stripe-mock (a local Stripe API server), nock (Node.js HTTP interceptor), or VCR cassettes (recorded responses replayed in tests). Each approach has trade-offs.
Testing
PayPal and Braintree both provide sandbox environments that mirror their production APIs. PayPal Sandbox uses test buyer/seller accounts. Braintree Sandbox provides test nonce values for different payment scenarios. Both support webhook testing for order completion and payment events. This guide covers setup, test credentials, automation patterns, and common gotchas.
Testing
Stripe subscription testing requires simulating billing cycles, plan changes, and edge cases that only appear over time. Stripe's test mode lets you fast-forward time, trigger immediate renewals, and test proration calculations without waiting for real billing cycles. This guide covers how to test subscription creation, upgrades, cancellations,
Testing
Stripe's test mode lets you run complete payment flows without real money. Test card numbers like 4242 4242 4242 4242 simulate successful payments, while other numbers simulate declines, insufficient funds, and 3D Secure authentication. This guide covers how to test the full checkout flow using Playwright, handle authentication
Testing
Stripe webhooks are HTTP POST requests Stripe sends to your server when payment events occur. Testing them requires replaying signed events against your handler without depending on real Stripe infrastructure. This guide covers stripe-cli for local forwarding, constructing test payloads in pytest, verifying webhook signatures, and running webhook tests
SRE
SLI, SLO, and error budget are the vocabulary of reliability engineering.