jsdom mount about enzyme

[ljharb]

On this line, wrapper is the button - perhaps you just want wrapper.simulate('click')?

[n7best]

Yea, everything works fine local. Trying to get t work with Travis. I want to make sure it works before adding more test.

[lelandrichardson]

@n7best is there any way you can figure out what that stacktrace is pointing to? undefined is not a function... it would be nice to know what it is thinking is undefined.

i see you're using webpack to bundle it. When you run it locally, is it also running it bundled with webpack?

[n7best]

Yea. Everything is same except for Travis I add
'''
if (process.env.TRAVIS) {
configs.browsers = ['Chrome_travis_ci'];
}
'''
To karma config to make chrome work. And all those error are from the one using mount. So I figure it's some where with Travis config where I manually insert nvm use 4 command where something still undefined

[ljharb]

@n7best you don't want a manual nvm use command anywhere for travis tho - https://github.com/n7best/react-weui/blob/master/.travis.yml#L12 is unnecessary due to https://github.com/n7best/react-weui/blob/master/.travis.yml#L4. (also, https://github.com/n7best/react-weui/blob/master/.travis.yml#L13 is unnecessary since travis always prints that out)

[n7best]

Ha I was just hoping that might be the problem since it doesn't work without those. So, yea those didn't help any thing. You can see (this build)[https://travis-ci.org/n7best/react-weui/builds/95716852] are without those and have same problem before I added those.

[lelandrichardson]

It would help to know what line it is throwing on and what it is trying to invoke that is undefined. I suspect it is something that webpack is doing but I'm not sure what that would be

[n7best]

@lelandrichardson I am running out of idea how to debug this thing since it's only happening with travis. I add debug info and sourcemap to this build where you can see which function is trigger the problem.

[lelandrichardson]

@n7best one thing i can see is that part of the stack trace is ReactPerf.js. Are you running the performance utils with react? I'm not sure if we've ever tested that. It could be causing some problems.

It seems like component.getPublicInstance() is what is failing, thus getPublicInstance does not exist. I'm not sure why that would happen :/