It's wrong. UI code isn't hard to unit test. It's borderline-impossible to integration test the state of the art in "controlling a browser to poke at your UI" i

It's wrong. UI code isn't hard to unit test. It's borderline-impossible to integration test the state of the art in "controlling a browser to poke at your UI" is woefully inadequate, as are the debugging mechanisms available when anything unexpected happens. And I'm talking about a single-browser suite of tests, not even trying to assess cross-browser testing, testing on the nigh-infinite number of (device-spec * OS version * "value added" OEM android garbage libraries * custom build of chrome) matrix that is mobile devices.