TikiTest records the scripts and arguments each step of the way in a test. But it does not record the way in which the user actually goes from one script to the next (i.e., which button, link or widget was clicked and in what way).
So, although TikiTests is able to verify that each script along the way produces the appropriate outputs, it cannot verify that this sequence of scripts can still be achieved through end user actions. All we know for sure is that it could be achieved at the time when the test was recorded, but if something has changed since (ex: the button needed to move from screen 1 to screen 2 was accidentally removed), there is no way to explicitly intercept that.
Of course, you can can write XPATH expressions which will test for the presence of a button which, we assume, will bring you from screen 1 to screen 2 when you press it. But we cannot test that pressing the button actually does that.
With Selenium, we can test for that, since Selenium actually creates user events in the browser (I think).
is able to check that a particular php script, invoked with particular arguments, will y