<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bhargav Shah</title>
    <description>The latest articles on DEV Community by Bhargav Shah (@bhargavshah).</description>
    <link>https://dev.to/bhargavshah</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F403041%2F0fd6f0ca-9edd-40ef-a542-24b2542edbc0.png</url>
      <title>DEV Community: Bhargav Shah</title>
      <link>https://dev.to/bhargavshah</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bhargavshah"/>
    <language>en</language>
    <item>
      <title>Testing React Context using react testing library</title>
      <dc:creator>Bhargav Shah</dc:creator>
      <pubDate>Tue, 09 Aug 2022 17:00:31 +0000</pubDate>
      <link>https://dev.to/bhargavshah/testing-react-context-using-react-testing-library-44b2</link>
      <guid>https://dev.to/bhargavshah/testing-react-context-using-react-testing-library-44b2</guid>
      <description>&lt;p&gt;Testing React components that are context consumers has typically been messy. The more context providers they need the messier it gets. Read on to explore this pattern which makes it crisp and declarative, and consequently makes TDD with React a bit better 👾&lt;/p&gt;

&lt;p&gt;&lt;a href="https://overcompiled.dev/post/testing-react-context-using-testing-library/"&gt;https://overcompiled.dev/post/testing-react-context-using-testing-library/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Do you use a pattern that helps you with this? Let me know!&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
