Skip to content

docs: fix discount fixture percentage keys #90

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.

Sign up for GitHub

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

Merged
carolinerg1 merged 1 commit into from
Aug 17, 2026
Merged

docs: fix discount fixture percentage keys #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,9 +81,9 @@ Example `test_fixtures.json`:
"quantity": 1
},
"valid_discount_code": "PROMO10",
"expected_discount_reduction": 1.0,
"expected_discount_percentage": 10.0,
"valid_discount_code_2": "PROMO20",
"expected_discount_reduction_2": 1.8,
"expected_discount_percentage_2": 20.0,
"valid_fixed_discount_code": "FIXED5",
"expected_fixed_discount_reduction": 5.0,
"known_customer": {
Expand Down Expand Up @@ -120,8 +120,8 @@ Example `test_fixtures.json`:

- `valid_item`: The SKU and expected price (in major units, e.g., `10.00`) of the item used in tests.
- **Discounts Configuration**:
- `valid_discount_code` & `expected_discount_reduction`: **Required** for basic discount flow tests. The code must be valid on your server, and the reduction is the expected amount in major units.
- `valid_discount_code_2` & `expected_discount_reduction_2`: **Optional**. Used for testing multiple discount codes applied sequentially. If your server does not support multiple discounts or you don't configure this, the corresponding test will be skipped.
- `valid_discount_code` & `expected_discount_percentage`: **Required** for basic discount flow tests. The code must be valid on your server, and the percentage is expressed as a number from 0 to 100.
- `valid_discount_code_2` & `expected_discount_percentage_2`: **Optional**. Used for testing multiple discount codes applied sequentially. If your server does not support multiple discounts or you don't configure this, the corresponding test will be skipped.
- `valid_fixed_discount_code` & `expected_fixed_discount_reduction`: **Optional**. Used for testing fixed-amount discounts. If your server only supports percentage discounts or you don't configure this, the test will be skipped.
- **Fulfillment Configuration**:
- `known_customer`: **Optional**. A buyer your server recognizes by email and stores addresses for, with the stored address contents (response-schema field names). Used by the stored-address injection, selection, and reuse tests; each skips if this is not configured. Address ids are read from your server's responses, so only the contents must match.
Expand Down
Loading