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

Testing Use Case: Reader of a test must be able to easily understand its intent and that of every step in the test

When a test break, the developer looking at it must be able to easily understand what was the correct behaviour that was tested. For example, if all the dev knows is that the output file differs in such and such way from the "correct" output, he shouldn't have to scratch his head in order to understand whether that difference matters or not (often, while the HTML output of a script changes slightly, the actual behavioural intent of the script is still fuilfilled... maybe the difference is just a different way of formatting the output...)

Page last modified on Tuesday 03 February, 2009 18:16:20 UTC

SourceHistoryComments

Search Wishes (subject only) [toggle]

Categorize Testing Use Case: Reader of a test must be able to easily understand its intent and that of every step in the test

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.