User Tools
uls:testsuite
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
uls:testsuite [2013-12-30 08:27] uls [Test Plan] |
uls:testsuite [2015-04-30 16:53] (current) uls [General structure of test sequences] |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| * ULS ticket tracking: threshold violations generate notifications and tickets. ULS users can work on those tickets and document their actions. | * ULS ticket tracking: threshold violations generate notifications and tickets. ULS users can work on those tickets and document their actions. | ||
| + | ----- | ||
| ==== Test Plan ==== | ==== Test Plan ==== | ||
| Line 51: | Line 51: | ||
| :TODO: an image to describe the test environment (test script, test server, directories, interactive analysis...) | :TODO: an image to describe the test environment (test script, test server, directories, interactive analysis...) | ||
| + | ----- | ||
| ==== Test Suites ==== | ==== Test Suites ==== | ||
| Line 56: | Line 57: | ||
| The test suites for the ULS versions: | The test suites for the ULS versions: | ||
| * [[uls:testsuite:version_180]] | * [[uls:testsuite:version_180]] | ||
| + | |||
| + | |||
| + | ----- | ||
| + | |||
| + | ==== General structure of test sequences ==== | ||
| + | |||
| + | :NOTE: This is of informational use for testers and has no general relevance for ULS. | ||
| + | |||
| + | General structure of test sequences: | ||
| + | |||
| + | * manually / explicitly specified | ||
| + | * domain-based specifications | ||
| + | * group-based specifications | ||
| + | |||
| + | Subsections: | ||
| + | * === (A) Specifications === | ||
| + | * define specifications | ||
| + | * specifications successfully defined? applied correctly? properly propagated? | ||
| + | * correct operation? | ||
| + | |||
| + | * === (B) Change === | ||
| + | * change specifications | ||
| + | * applied correctly? properly propagated? | ||
| + | * correct operation? | ||
| + | |||
| + | * === (C) Deactivation === or === (C) Removal === | ||
| + | * deactivate specifications | ||
| + | * applied correctly? properly propagated? | ||
| + | * correct operation? | ||
| + | |||
| + | Typical table for test results, use 4 char (abbreviation of test section) and 3 digits to give a unique expression. | ||
| + | |||
| + | {| | ||
| + | ! Test | ||
| + | ! Description | ||
| + | ! Result | ||
| + | ! Notes | ||
| + | |- | ||
| + | | XXXX dddd | ||
| + | | <section header>: <what> <result> | ||
| + | | style="color:green" | passed or :TODO: or FIXME | ||
| + | | <remark> | ||
| + | |} | ||
| + | |||
| + | |||
| + | RTIM Retention TIMe | ||
| + | AGGR Aggregation | ||
| + | NTFY Notification | ||
| + | SECU Security | ||
| + | UTTR ULS Ticket Tracking | ||
| + | |||
uls/testsuite.1388388473.txt.gz ยท Last modified: 2014-01-21 08:43 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
