<?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>리트라이 on Codeslog</title>
    <link>https://www.codeslog.com/tags/%EB%A6%AC%ED%8A%B8%EB%9D%BC%EC%9D%B4/</link>
    <description>Recent content in 리트라이 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.150.0</generator>
    <language>ko</language>
    <lastBuildDate>Wed, 22 Jul 2026 01:30:00 +0900</lastBuildDate>
    <atom:link href="https://www.codeslog.com/tags/%EB%A6%AC%ED%8A%B8%EB%9D%BC%EC%9D%B4/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>트레이스·디버깅·리트라이로 원인 추적</title>
      <link>https://www.codeslog.com/posts/frontend-testing-playwright-debug/</link>
      <pubDate>Wed, 22 Jul 2026 01:30:00 +0900</pubDate>
      <guid>https://www.codeslog.com/posts/frontend-testing-playwright-debug/</guid>
      <description>테스트가 CI에서만 깨질 때, 무엇을 봐야 할까요? Playwright의 트레이스 뷰어와 디버깅 도구로 실패의 진짜 원인을 추적합니다.</description>
    </item>
  </channel>
</rss>
