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
Print

Dev needs to test that it is in fact possible for the user to move from a certain page to another

The dev wants not only to test that a particular HTTP request sent to Tiki produces the expected result. He also wants to verify that it's actually possible for an end user to issue that HTTP request from another given page.

For example, if you are testing page editing, you want to check that tiki-editpage.php displays what it should when it is invoked with appropriate CGI arguments.

But you also want to verify that it can indeed be invoked with the proper arguments, from a given tiki-index.php page with given arguments.

Let's take a simple (albeit unlikely case). Suppose I do a change to the code which ends up removing the Edit which, previously, was visible at the bottom of a given tiki-index.php page. When that happens, the test have to be able to spot that.

Page last modified on Tuesday 03 February, 2009 16:04:50 UTC

SourceHistoryComments

Search Wishes (subject only) [toggle]

Categorize Dev needs to test that it is in fact possible for the user to move from a certain page to another

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.