-
Notifications
You must be signed in to change notification settings - Fork 442
Testing with VCR
Victor Pereira edited this page Jul 19, 2019
·
11 revisions
In our CI environment, we don't have the backend running and therefore we are using VCR to reply previous recorded HTTP sessions between frontend and backend.
CAVEAT:
We have a configuration global named global_write_through
if data will be sent to backend or not. This configuration is controlled on spec/support/vcr.rb
. To be able to generate or refresh an already generated cassette, you will need to enable the global_write_through
before to run a spec. Important do not run the whole suite with global_write_through
enabled. Instead run just the specific spec needing a new cassette.
- Development Environment Overview
- Development Environment Tips & Tricks
- Spec-Tips
- Code Style
- Rubocop
- Testing with VCR
- Authentication
- Authorization
- Autocomplete
- BS Requests
- Events
- ProjectLog
- Notifications
- Feature Toggles
- Build Results
- Attrib classes
- Flags
- The BackendPackage Cache
- Maintenance classes
- Cloud uploader
- Delayed Jobs
- Staging Workflow
- StatusHistory
- OBS API
- Owner Search
- Search
- Links
- Distributions
- Repository
- Data Migrations
- next_rails
- Ruby Update
- Rails Profiling
- Installing a local LDAP-server
- Remote Pairing Setup Guide
- Factory Dashboard
- osc
- Setup an OBS Development Environment on macOS
- Run OpenQA smoketest locally
- Responsive Guidelines
- Importing database dumps
- Problem Statement & Solution
- Kickoff New Stuff
- New Swagger API doc
- Documentation and Communication
- GitHub Actions
- How to Introduce Software Design Patterns
- Query Objects
- Services
- View Components
- RFC: Core Components
- RFC: Decorator Pattern
- RFC: Backend models