title: React-Admin: Why the non-descriptive class names?
body: <blockquote>
    <p>I am hoping someone can shed some light on what is likely a very basic <code>react</code> question.  </p>
  </blockquote>
  
  <p><strong>Within <code>react-admin</code>based web apps, is it typical/expected to see <code>class names</code>(below)?</strong></p>
  
  <pre class="lang-js prettyprint-override"><code>class="jss136 jss138 jss125 jss127"
  </code></pre>
  
  <p>I am working on a project to setup some <code>e2e</code> framework using <code>selenium</code> for a <code>react-admin</code> site and it has proven to be challenging therefore I am curious if this is fairly typical to see in <code>react-admin</code> or if there may be something our development team could do differently that would provide more descriptive class names for interacting with elements?</p>
  
  <p>Any information/insights into this or other tips you may have related to <code>e2e</code> testing with <code>selenium</code> within <code>react-admin</code> would be much appreciated.</p>
  
  <p>Thank you,<br>
  Bob</p>