Less Less pain ainful l E2E tes ests s wit ith Cy Cypres ess.io Pavel Kruhlei, FOSSDEM 2019
Quality Engineering Lead in fintech startup in Amsterdam 10+years in QA. 5 in automation. About me DevTestSecOpsWhatewer, big fan of serverless Free time: bouldering, drinking Belgium beer
What’s wrong with Selenium?
What else?
JS (TS) framework for test automation What is Runner/Debugger app Cypress? SAAS for reporting and balancing
Why Cypress?
Cypress and it’s dev-obsession • Bundled tools • Reporters (junit, teamcity etc)
Cypress and it’s dev-obsession • Extendable by plugins • Easy setup • CI-ready • Debugging • Stubs, spies and clocks • Automatic waits
Unit Test Integrstion layers E2E
Unit tests
Integration test
E2E Tests Test suites per business areas (how we Locators and Flows Sub-flows Page-Objects build it) Methods
Chrome-only Its a test automation tool still, not a Swiss army knife (no spider, Traid- performance tests or 3rd party tests) offs Single-browser, single tab Same domain pages
Stub/not Stub Deterministic tests Independent tests Cypress test No XPATH strategy Control application state Do not test 3 rd parties Multiple assertions are fine
Recommend
More recommend