Webship-js 2.0.16 tells you when an element is not on the page, instead of blaming a slow page. Found by following every step pack's README from a new project on real sites.
Fixed since Webship-js 2.0.15:
- A step that waits for an element that is not on the page now says that nothing on the page matched within the wait. Before, it said "the page took too long to respond", though the page had answered at once. A hidden, covered or disabled element now says so too; a page load past its timeout keeps the old wording (#538)
Documentation:
- The FAQ answers "Can I load several step packs in one project?": packs for one site go in one profile, packs for two sites get one profile each, and
npm run test:packschecks the first case against every pack on npm (#534) - The step docs of
I click,I checkandI uncheckdescribe what 2.0.13 changed (#536)
Install: npm install --save-dev webship-js@2.0.16, then npx init-webship-js for a new project.