<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>E2E on Codeslog</title>
    <link>https://www.codeslog.com/en/tags/e2e/</link>
    <description>Recent content in E2E on Codeslog</description>
    <image>
      <title>Codeslog</title>
      <url>https://www.codeslog.com/images/default-cover.png?v=20260114T1436</url>
      <link>https://www.codeslog.com/images/default-cover.png?v=20260114T1436</link>
    </image>
    <generator>Hugo -- 0.168.0</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 29 Jul 2026 15:01:36 +0900</lastBuildDate>
    <atom:link href="https://www.codeslog.com/en/tags/e2e/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Visual Regression Testing — Screenshot Comparison</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-visual-regression/</link>
      <pubDate>Wed, 29 Jul 2026 15:01:36 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-visual-regression/</guid>
      <description>&amp;#39;The feature works but the layout broke.&amp;#39; Catch what only eyes used to catch: implement visual regression tests with Playwright screenshot comparison, stable snapshots, and the environment trap to avoid.</description>
    </item>
    <item>
      <title>Accessibility E2E — Scanning with @axe-core/playwright</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-axe-e2e/</link>
      <pubDate>Mon, 27 Jul 2026 14:38:51 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-axe-e2e/</guid>
      <description>Catch page-wide accessibility violations automatically, in a real browser. What axe-core is and how it works, how to integrate it into Playwright E2E, and what automation catches — and can&amp;#39;t.</description>
    </item>
    <item>
      <title>Traces, Debugging, and Retries — Tracking Down the Cause</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-playwright-debug/</link>
      <pubDate>Wed, 22 Jul 2026 01:30:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-playwright-debug/</guid>
      <description>What do you look at when a test fails only on CI? Playwright&amp;#39;s trace viewer and debugging tools track the real cause — with evidence, not guesswork — and turn retries into a signal instead of a fix.</description>
    </item>
    <item>
      <title>Fixtures, Auth Reuse, and Parallel Runs</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-playwright-fixtures/</link>
      <pubDate>Tue, 21 Jul 2026 01:25:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-playwright-fixtures/</guid>
      <description>Repeating the same setup in every test? Playwright&amp;#39;s custom fixtures (base.extend) and Page Object pattern remove it, storageState logs in once, and fullyParallel keeps the suite fast and isolated.</description>
    </item>
    <item>
      <title>Locators and auto-wait — Taming Flaky Tests</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-playwright-locators/</link>
      <pubDate>Sat, 18 Jul 2026 23:06:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-playwright-locators/</guid>
      <description>Why E2E tests fail only sometimes, and the actual fix. Understand Playwright locators, auto-wait, and strict mode, and cut flakiness at the root with robust selectors.</description>
    </item>
    <item>
      <title>Getting Started with Playwright E2E — Your First Scenario</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-playwright-intro/</link>
      <pubDate>Sat, 18 Jul 2026 02:25:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-playwright-intro/</guid>
      <description>E2E verifies whole user flows in a real browser. Install Playwright, understand the webServer config, and write and pass your first scenario — with a clear role split against unit and component tests.</description>
    </item>
    <item>
      <title>Testing Terms, All in One Place — A Frontend Testing Glossary (Appendix)</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-glossary/</link>
      <pubDate>Sat, 04 Jul 2026 22:30:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-glossary/</guid>
      <description>From unit tests to flaky, fixtures, and MCP — every term in the Frontend Testing, Done Right series, explained for beginners and ordered the way you&amp;#39;ll meet them. Bookmark this page and come back whenever a word looks unfamiliar.</description>
    </item>
    <item>
      <title>Why Frontend Testing, Why Now — A Seatbelt for the AI Era</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-why-now/</link>
      <pubDate>Fri, 03 Jul 2026 16:33:17 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-why-now/</guid>
      <description>The faster AI writes code, the more testing matters. In this opener of the Frontend Testing, Done Right series, we cover what tests really give you, pyramid vs. trophy strategy, and the full curriculum ahead.</description>
    </item>
  </channel>
</rss>
