<p dir="auto">I originally left a comment in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="107717775" data-permission-text="Title is private" data-url="https://github.com/facebook/react/issues/4936" data-hovercard-type="issue" data-hovercard-url="/facebook/react/issues/4936/hovercard" href="https://github.com/facebook/react/issues/4936">#4936</a>, but I felt this might be better as a separate issue.</p>
<blockquote>
<p dir="auto">I completely agree with the rationale behind no backing instances and no refs for stateless components. I want to use pure stateless components as much as possible.</p>
<p dir="auto">However, I'm running into instances where testing stateless components gets tricky. For the most part, using the shallow renderer to render a stateless component has been fine. I can then make assertions on expected props and children. To reduce the duplication, I abstract out the shallow renderer process to a helper function.</p>
<p dir="auto">When, I want to test events, though, I have to take a different route. If my component takes an <code class="notranslate">onClick</code> prop, then I wrap it in a class component, so I can access the DOM node to simulate my click event. Again, this isn't a huge deal because I can abstract out the wrap/render process into a helper function.</p>
<p dir="auto">I bring all this up because I feel that it would be nice to have better facilities in <code class="notranslate">TestUtils</code> for stateless components. I don't think the answer is allowing <code class="notranslate">ReactDOM.findDOMNode</code> to work on stateless components because that opens up it to abuse in normal application code. Are you open to allowing extra functions in <code class="notranslate">TestUtils</code> to simplify the process of testing stateless components? Or am I creating a code smell in my testing?</p>
<p dir="auto">I'd be happy to create a PR for <code class="notranslate">TestUtils</code> if you think some more helper functions for stateless components would be beneficial.</p>
</blockquote>
<p dir="auto">Hi,</p>
<p dir="auto">I have a fairly trivial application which was running on ReactJS 0.14.x. Since I've moved it to 15rc1, it continues to work perfectly in Chrome. However, in IE11, in appears to render critical parts empty. The relevant piece of code where I'm failing is here:</p>
<p dir="auto"><a href="https://github.com/technion/erlvulnscan/blob/master/frontend/assets/erlvulnscan.jsx#L37">https://github.com/technion/erlvulnscan/blob/master/frontend/assets/erlvulnscan.jsx#L37</a></p>
<p dir="auto">There is no error output on the debug console. The DOM explorer appears to just render it with missing data.</p>
<div dir="auto"></div>
<p dir="auto">You can see the application with the relevant behaviour running live at: <a href="https://erlvulnscan.lolware.net" rel="nofollow">https://erlvulnscan.lolware.net</a>. Enter any network (127.0.0.0 will yield the fastest return) to see the issue.</p>
<p dir="auto">Edit: For non IE users, you can see a SS here: <a href="http://imgur.com/i9TciqZ" rel="nofollow">http://imgur.com/i9TciqZ</a></p>