@Fancy - The 1) is probably that you've disabled sandboxing and your tests are a bit incorrectly structured. I guess the "init" event is fired asynchronously. But all the test code is inside of "init" handler. So Siesta think test has completed already, and then suddenly there are new calls on test instance. You need to first wait for the "init" event to fire, and then continue the test. Check the "siesta/examples/2.ui-tests/grid/editing.t.js" for example. But all these are my guesses, for something real, please post a reproducible test case.
Please also download the latest release, as problems you are reporting might be already fixed.
And move the other questions to separate threads.