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 needs to be able to modify an existing test

Devs must be able to change a test after it has been created and put into the central repository of tests (possibly by someone else).

For example, it could be that the steps of the test now need to be carried out in a slightly different way, by pushing different buttons at different times, or invoking different scripts with different arguments.

Or, it could be that there is a new behaviour that was introduced which should be tested by that test.

Or, it could be that a script now generates a slightly different output that still fulfills the same intent as before, and that therefore, the assertion checks on the output have to be changed.

All of the above need to be supported.


Page last modified on Tuesday 03 February, 2009 18:21:29 UTC

Search Wishes (subject only) [toggle]

Categorize Testing Use Case: Dev needs to be able to modify an existing 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.