78d2a5e3c0
ref https://linear.app/tryghost/issue/CFR-13 - enabled saving traces on browser test failure; this makes troubleshooting a lot easier - updated handling in offers tests to ensure the tier has fully loaded in the UI (not just `networkidle`) - updated publishing test to examine the publish button reaction to the save action response instead of a 300ms pause In general, our tests use a lot of watching for 'networkidle' - and sometimes just raw timeouts - which do not scale well into running tests on CI. In particular, 'networkidle' does not work if we're expecting to see React components' state updates propagate and re-render. We should always instead look to the content which encapsulates the response and the UI updates. This is something we should tackle on a larger scale. |
||
---|---|---|
.. | ||
donations.spec.js | ||
member-actions.spec.js | ||
offers.spec.js | ||
tiers.spec.js | ||
upgrade.spec.js |