-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Omniscient 4.0 Components Seem to Not Working with React Test Utilities #123
Comments
Hi! Thanks for getting in touch. How are you running these tests? mocha+babel, babel-cli, jest etc? |
So I got this running, but I'd like to see your setup in total to be able to debug further. I patched up jsdom like in our While I don't know what's causing it to fail, it seems to have to with jsx - replacing |
@torgeir Thank you for your help. Yes, the test runs if I replace |
Handle component creator's result being new'ed from within react 0.14, #123
This is resolved in master, have a go with this
We have some other minor-stuff in master as well that needs some tests before we release this. |
This is now released in https://github.com/omniscientjs/omniscient/releases/tag/v4.1.0 |
Hello, it seems that React components created by Omniscient 4.0 do not work well with React 0.14 test utilities. In my tests, TestUtils.renderIntoDocument() runs correctly with components created by React.createClass(). If I input a component created by Omniscient, it always return null.
Please run the following tests for more details. I hope this issue will be resolved soon.
Thank you and sorry for my bad English.
The text was updated successfully, but these errors were encountered: