catalyst/core/.env.test.example at f7daa8e101ca4bec20f5b9ce7c48c1b0275b3b72 · bigcommerce/catalyst · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
# This file should hold any environment variables specific to test execution.
# Any overlapping variables in here will overwrite variables from the other .env files.
# For example, if BIGCOMMERCE_CHANNEL_ID=1 in .env.local, but BIGCOMMERCE_CHANNEL_ID=5 in this file, the test environment will use BIGCOMMERCE_CHANNEL_ID=5

# Access token client ID and client secret are required for JWT login tests. If not provided, tests that require these will be skipped.
# If provided, ensure the API account associated with this client ID/secret pair has the following scope:
#   - Customers login: login
BIGCOMMERCE_CLIENT_ID=
BIGCOMMERCE_CLIENT_SECRET=

# Base URL for all tests. This should always be set. It is recommended to run tests against a production build.
# If not set or undefined, it will default to 'http://localhost:3000'
PLAYWRIGHT_TEST_BASE_URL=http://localhost:3000

# If true, no tests will execute that require modifying/deleting any data on your store.
# This is particularly useful if you want to run the tests against a live store and avoid test data being visible to any customers.
# If this is false, you should only run tests against a staging store where test data is okay.
TESTS_READ_ONLY=false

# Locale to use during test execution
TESTS_LOCALE=en

# The fallback locale to use in the occurence of missing translation keys in the selected TESTS_LOCALE
# This should match the default locale you have set for your storefront
TESTS_FALLBACK_LOCALE=en

# An existing customer account to use for all tests - use this if you don't want tests to create a new customer account.
# If TESTS_READ_ONLY is `true`, then any test requiring a customer will be skipped if these values are not set.
TEST_CUSTOMER_ID=1
TEST_CUSTOMER_EMAIL=example@test.com
TEST_CUSTOMER_PASSWORD=Password1

# Used to create/update/delete store data for testing purposes
# Some tests will not pass without a BIGCOMMERCE_ACCESS_TOKEN, even with TESTS_READ_ONLY set to true
# This is due to the test API client sending GET (read-only) API requests
# Create a token with the following scopes:
#   - Content: read-only
#   - Products: read-only
#   - Channel listings: read-only
#   - Channel settings: read-only
#   - Information & settings: read-only
#   - Customers: read-only
#   - Orders: read-only
# When TESTS_READ_ONLY is false, you'll need additional scopes:
#   - Products: modify
#   - Content: modify
#   - Customers: modify
#   - Marketing: modify
#   - Orders: modify
BIGCOMMERCE_ACCESS_TOKEN=

# The default product ID to use for tests. This needs to be a product without variants (simple)
# This is optional, but recommended. If left empty, tests that require a product will be skipped if TESTS_READ_ONLY is true
DEFAULT_PRODUCT_ID=

# The default product ID to use for tests that require a complex product. This product must have at least 1 variant.
# This is optional, but recommended. If left empty, tests that require a complex product will be skipped if TESTS_READ_ONLY is true
DEFAULT_COMPLEX_PRODUCT_ID=