# Why UI Components Have Two Users--and How to Test Them

DevFeed: [Why UI Components Have Two Users--and How to Test Them](<https://devfeed.tech/articles/avoid-the-test-user-51734.md>)

Original publisher: [Read original article](<https://kentcdodds.com/blog/avoid-the-test-user>)

Published: 2019-05-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [Kent C. Dodds Blog](<https://devfeed.tech/sources/kent-c-dodds-blog.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [React](<https://devfeed.tech/topics/react.md>), [ui](<https://devfeed.tech/topics/ui.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [react](<https://devfeed.tech/tags/react.md>), [software](<https://devfeed.tech/tags/software.md>), [testing](<https://devfeed.tech/tags/testing.md>), [ui](<https://devfeed.tech/tags/ui.md>)

## AI overview

The article explains that UI components serve both end users and developers. It argues that tests should reflect how software is actually used rather than focusing on implementation details, while distinguishing changes to the developer API, user experience, and internal implementation.

## Source excerpt

How your UI code has only two users, but the wrong tests can add a third