Possibility to opt out of removing `data-testid` from icons on production

[hbj]

Summary

Removing the data-testid from icons only for production is very confusing because if you run e2e tests with the production version, as we do, you might have your tests running locally when implementing them, because you use the dev version, but have them fail on CI that uses the prod version. If you forget about this point you might have to wait for the CI to finish to figure out the issue. This also makes debugging very difficult unless you're aware of this subtlety.

Is it possible to add some flag/env var to opt out of removing the data-testid?

Related PR.

Examples

No response

Motivation

No response

Search keywords: icons, testid, data-testid

[Janpot]

The decision to only show testids in dev was an idea to find middle ground between users relying on them for tests and avoiding them ending up in production ssr content. For now the remedy would be to provide your own data-testid to the icons you want to test. We're exploring a property to enable this testid globally.

[hbj]

This property is exactly what I'm asking for, thanks 🙌

[nicobatalla]

I am currently updating a production app to MUI v7 and this is the main blocker we are getting at this point. We do use a few of the default data-testid in our e2e suites, and it would be much appreciated to be able to opt-out

[koooge]

Hi there, I got the same problem while upgrading MUI. Another idea, what about removing data-testid from development, too?

[gabrielsarriavillada]

Hi! Same as other devs have mentioned, we are using data-testid in our e2e testing. Is there an ETA for putting back the data-testid, or at least the flag to enable it, please? Thanks in advance.

[anthonyma94]

Bump, bringing it back would be great.

[JBeaudaux]

Indeed, this was a very useful feature. Any timeline to bring it back?

[leonardocouy]

This is the only thing that we need in a project to upgrade from v6 to v7. Please, consider bringing it back guys!