Forum OpenACS Q&A: Re: Re: Re: How do I speedup tclwebtest ?

Collapse
Posted by Gustaf Neumann on
Åsmund has written the recorder as a byproduct of his bachelor work, since writing long tclwebtest scripts was to boring. It will need some cleanup and beautification, so it will take a little bit more time until it is released.

yesterday, we were discussion the dependency on localization. Currently, the approach will only work for one locale. There are two problem areas:

  • detecting page failure: When use site specific "pretty" return error pages (e.g. for 404 not found), the http status code will be 200 (try the error message on openacs.org)

  • dynamic links: when new items are created, it is much easier to find these depending on the link label than on the ids, which will change. In some cases, the links will be fine.

The first problem could be solved by either by changing/programming around this behavior of the aolserver (see discussions on the aolserver list) or by adding hidden fields to the return pages. Currently the recorder checks the title of the page, which works pretty well but is locale dependent. The second problem is more serious. Introducing IDs for every anchor etc. does not seem realistic.

Do the tclwebtester or selenium testers have some thoughts / best practice experiences about this?