React: Run at least a subset of the tests in-browser before releases
Frankly, it scares me a little that a substantial IE text node bug made it through into a release candidate. Some of the tests could _fairly easily_ be run on SauceLabs or a similar service to do actual browser verification.
probablyup
All 4 comments
Is this not precisely what prereleases are for? To capture bugs that unit tests and the team has missed in development?
iamdustan
on 11 Mar 2016
This is definitely something we want to do.
Please refer to #5703 for the related discussion.
I鈥檓 not sure what the specific roadblocks are, but it鈥檚 better to ask in the existing issue.
gaearon
on 11 Mar 2016
@iamdustan absolutely not. Relying on the community to catch core bugs is ludicrous
probablyup
on 11 Mar 2016
Yea, this was a bad one that got through. We should have caught it. There are a couple things we could do differently for that particular one (including but not limited to browser testing). Thanks for bringing it up - it's definitely on our minds.
zpao
on 11 Mar 2016
Related issues
zpao
路
3Comments
MoOx
路
3Comments
DimitarChristoff
路
3Comments
bloodyowl
路
3Comments
huxiaoqi567
路
3Comments
Most helpful comment
Yea, this was a bad one that got through. We should have caught it. There are a couple things we could do differently for that particular one (including but not limited to browser testing). Thanks for bringing it up - it's definitely on our minds.