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

Testing Use Case: Dev wants to write a series of related and very similar tests

Say the dev is writing tests to verify that authentication always happen correctly, no matter the circumstances. He may easily have to write a dozen of individual tests which carry out more or less the same actions and verifications in slightly different circumstances (ex: empty user db, blank user name, blank password, etc...).

As much as possible, the dev wants the common parts of these tests to be modularised (ex: use the same code or XPATH expression to verify whether or not the userid and pwd were accepted), so that he doesn't have to do it 12 times, and so that he doesn't need to change it in 12 places if it later needs to change.


Page last modified on Tuesday 03 February, 2009 15:56:58 UTC

Search Wishes (subject only) [toggle]

Categorize Testing Use Case: Dev wants to write a series of related and very similar tests

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.