af4d7b4938
no issue - When Ghost is running in a test environment, it is configured with an invalid Stripe key that looks like `sk_test***`. In this case the migrations try runnig creating request to Stripe, which fail. The failures pollute the output, which makes other valid errors lost. - An example of such error log is following: ``` Invalid API Key provided: sk_test_******ripe ---------------------------------------- Error: Invalid API Key provided: sk_test_******ripe at res.toJSON.then.StripeAPIError.message (/home/naz/Workspace/Ghost/Ghost/node_modules/stripe/lib/StripeResource.js:214:23) at processTicksAndRejections (node:internal/process/task_queues:96:5) ``` - There doesn't seem to be a good reason to do migrations in the test environment. Skipping them as a special case to fix the output pollution problem seems like a right solution |
||
---|---|---|
.. | ||
unit/lib | ||
utils | ||
.eslintrc.js | ||
hello.test.js |