-
-
Notifications
You must be signed in to change notification settings - Fork 724
Stripe testing
David Cook edited this page Jan 18, 2024
·
1 revision
Stripe tests use real requests to test against the Stripe API. Rather than execute these every time, the responses are recorded to a fixture file. These need refreshing from time to time, particularly when upgrading Stripe versions. There is a helper script to do this easily:
script/test-stripe-live
A Stripe account is required to test against the API. Two secret variables are required:
# add these lines in .env.test.local
STRIPE_SECRET_TEST_API_KEY="sk_test_••••"
STRIPE_CLIENT_ID="ca_••••"
For those that have access to BitWarden, a shared key and client ID may be found under Stripe Secret Test API Key
These secrets are filtered out in vcr_setup.rb and will not be saved in the fixture files.
Development environment setup
- Pipeline development process
- Bug severity
- Feature template (epic)
- Internationalisation (i18n)
- Dependency updates
Development
- Developer Guidelines
- The process of review, test, merge and deploy
- Making a great commit
- Making a great pull request
- Code Conventions
- Database migrations
- Testing and Rspec Tips
- Automated Testing Gotchas
- Rubocop
- Angular and OFN
- Feature toggles
- Stimulus and Turbo
Testing
- Testing process
- OFN Testing Documentation (Handbooks)
- Continuous Integration
- Parallelized test suite with knapsack
- Karma
Releasing
Specific features
Data and APIs
Instance-specific configuration
External services
Design