-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/audit supplier #172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Conversation
|
|
||
| audit: | ||
| secret_key: <%= ENV.fetch('AUDIT_SECRET_KEY', 'test_secret') %> | ||
| host: http://localhost:9292 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't actually hit the servers on test, do we?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, but the full YAML is here to put things through its paces
- connection_timeout - invalid_json - wrong_json
…sts) Return proper 404 response when 404
which returns an array of "fixtures/audit/property.json" with "identifier" being set to success, connection_timeout, etc ...
Otherwise, "base_currency = self.to_currency(base_currency)" becomes nil
Update PropertySynchronisation usage based on e1a33dd
18ffd3d to
f142eed
Compare
|
Rebased with |
Supersede #123
Audit supplier server is a rack app serving static jsons from
spec/fixtures/auditWhen request param
property_id(quote, book) orreservation_number(cancel) is an error likeconnection_timeout, the rack server will respond accordingly to simulate the error. i.e. requests for a specific property or reservation will always get the same response.Sync workers will hit a
/spec/fixtures/audit/properties.jsonurl, which serves a list of properties withproperty_idvalues fromsuccess,connection_timeout, ...When consumers search and book, certain Audit properties (e.g.
property_id: success) will always succeed; and certain Audit properties (depending onproperty_id) will always hit the same error.When consumer try to cancel the booking, depending on the
reference_number, the cancellation will always succeed or encounter an error