Fullscreen
[Show/Hide Right Column]

Close
noteNote
This page is to document "what Tiki should do". For feature documentation (what Tiki does), please see corresponding page on doc site

How to reuse parts of a script in other scripts

This is necessary for use case:


Often, we need to use the same assertion check, or the same inittialisation code, or the same or almost sequence of steps in different tests. In cases like that, it's better to write one bit of code or test specification and then invoke it in different tests.

With phpunit+Selenium, this is trivial to do. You just write a PHP method and call it from different tests.

With TikiTests, the only place where you can do this easily, is for specifying the start state of the app. Here, you may be able to reuse the same profiles or DB dumbs across different tests. But that's all. You can't reuse assertions, and you can't reuse sequences of screens. Well, you could, but you would have to add a lot of new features to TikiTests to support that.

Related

Page last modified on Friday 15 May, 2009 12:51:05 UTC

Search Wishes (subject only) [toggle]

Categorize How to reuse parts of a script in other scripts

Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.