When running Lightning Testing Service tests, the impact of the LockerService is evident such as not being able to see the DOM nodes of a lightning:... component (different namespace) wrapped by one of my components (including via the JavaScript debugger).
We also want to build Selenium UI tests and Selenium tests need to find buttons etc. across the entire DOM. Does the LockerService make Selenium tests impossible?
All details of why or why not appreciated.
DOM element encapsulation is applied by Locker Service only during the component's life cycle. In other words, only when a component(controller/renderer/helper) tries to access DOM elements, Locker Service(LS) will apply filtering to restrict access to current component's namespace.
That should not affect Selenium UI tests, both for Selenium webdriver and Selenium RC. Webdriver will be executing outside of the component's lifecycle, like an external entity. LS will not interfere. Similarly, selenium RC javascript will be executing in system mode and will not be restricted by LS.
