testutil component destruction issue when API versions differ

[forcedotcom]

testutil component destruction issue when API versions differ

[esalman-sfdc]

Thanks @maxwellmstein for reporting the issue and sharing your approach to work around it.

By the way, is there are reason you aren't moving your code to version 40 to ensure everything is running inside a locker?

[maxwellmstein]

Yeah - for production builds all components will be v.40. I'm using a Redux store and the sweet chrome devtoolbar for it relies on the store being accessible on the window. So I have that one component at v.39 for development.

I think this issue would occur if you created components outside your namespace as well though, right? Say if I wanted to create some standard components to test my custom components interaction with them.

[esalman-sfdc]

Yes, basically when you access a component which isn't in the same locker (different namespace or below version-40), lockerService returns a SecureComponentRef wrapper instead of SecureComponent. SecureComponentRef's interface is alot more restrictive.

I do agree that clearRenderedTestComponents should be updated to support deletion of any component :)

[esalman-sfdc]

Update: For Winter'18, destroy() has been added to SecureComponentRef meaning that the current logic in the test util of LTS should start working as-is for components running without locker or from other namespaces. Related LockerService work-item W-4099006.