User Tools
uls:testsuite:version_180
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
uls:testsuite:version_180 [2014-01-23 12:01] uls |
uls:testsuite:version_180 [2014-01-29 08:14] (current) uls [Test Scenarios] |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| **boundary tests** are made to verify the correct processing of e.g. very small and very large values. | **boundary tests** are made to verify the correct processing of e.g. very small and very large values. | ||
| - | The **general tests** are based on values derived from the current number of seconds | + | **continuous tests** are based on values derived from the current number of seconds |
| - | * of the current hour | + | * within the current hour |
| - | * of the current day and | + | * within the current day |
| - | * of the current week (since 00:00 of last monday) | + | * within the current week (since 00:00 of last monday) and |
| + | * within the current month | ||
| - | These values are specifically converted and calculated to cover the most common scenarios. | + | These values are specifically prepared and calculated to cover the most common scenarios. |
| In combination with **threshold** definitions they are used to test the firing of **notifications** for threshold violations | In combination with **threshold** definitions they are used to test the firing of **notifications** for threshold violations | ||
| The notifications will contain replaced static and dynamically calculated embedded **placeholders** in their message bodies. | The notifications will contain replaced static and dynamically calculated embedded **placeholders** in their message bodies. | ||
| - | These values will also be used for the check of the **aggregation** of values. | + | These values will also be used for the check of the **aggregation** or **compression** of values. |
| Reports are used to check the different expected results and to check the **report** functionality itself. | Reports are used to check the different expected results and to check the **report** functionality itself. | ||
| Line 34: | Line 35: | ||
| * do the necessary [[uls:testsuite:version_180:preparations]] | * do the necessary [[uls:testsuite:version_180:preparations]] | ||
| - | ---- | + | The test cases are separated by function in different sections: |
| - | + | ||
| - | + | ||
| - | ==== Test Cases ==== | + | |
| - | + | ||
| - | These are the different sections where test cases are set up: | + | |
| * administrative settings and tests in [[uls:testsuite:version_180:admin_settings]] | * administrative settings and tests in [[uls:testsuite:version_180:admin_settings]] | ||
| Line 48: | Line 44: | ||
| * notifications in [[uls:testsuite:version_180:notifications]] | * notifications in [[uls:testsuite:version_180:notifications]] | ||
| * deletion of values after elapsed [[uls:testsuite:version_180:retention]] | * deletion of values after elapsed [[uls:testsuite:version_180:retention]] | ||
| + | |||
| ---- | ---- | ||
uls/testsuite/version_180.1390474867.txt.gz · Last modified: 2014-01-23 12:01 by uls
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
