Your QA engineer could use a framework like CodeceptJS (http://codecept.io/ http://codecept.io/) and get back the "sync behavior", mostly. If the app you're te

Your QA engineer could use a framework like CodeceptJS (http://codecept.io/ http://codecept.io/) and get back the "sync behavior", mostly. If the app you're testing is messy, some of the test code will have to be injected into the browser by webdriver (so obligatory Javascript, and oblygatory async for getting the results back...) and some (hopefully most!) will run outside, in the test-runner, so JS ends to be the only sane option if you don't want to write "Python with strings of JS sprinkled around". Also, webdriver itself is a mess with a horrible API forcefully riding another bigger mess (the browser adapters and browser itself), riding a top another mess (your app, however non-messy you imagine it to be, it's still a soup of crap running though the bowels of the browser)... so no "clean" solution here even if you're using Python. Probably the way out of "webdriver testing hell" is to use a frontend framework with good testing support and write good front-end unit-tests: but they will obviously be Javascript :)