Test Automation: From Zero To Hero
summary
New frontend components force a rewrite so a fresh framework is built in about one and a half years using C# + Selenium + nUnit, with selectors generated from component context and interactions limited to component‑specific methods. Setup and teardown move to APIs, navigation switches from UI clicks to URLs, and tests run in CI with parallelization. The team reports migrated thousands of tests, reduced flakiness, faster runs, and clearer failure signals so broken builds mean real bugs or needed test updates.
AI-written summary · about
chapters (5)
related talks
26mImplementing a test suite in an existing Frontend application
35mBuild an automation framework... with a developer mindset
55mModern Web Testing: Going Beyond Selenium
37mAdvanced Test Automation Techniques for Responsive Apps and Sites
18mEffective Test Automation Framework Design
41mAdvanced test automation techniques for responsive apps and sites
53mModern Web Testing: Going Beyond Selenium
38mModern Web Testing: Going Beyond Selenium
