This page (revision-34) was last changed on 26-Nov-2015 17:52 by Albrecht Striffler

This page was created on 26-Oct-2012 10:15 by unknown

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
34 26-Nov-2015 17:52 7 KB Albrecht Striffler to previous
33 26-Nov-2015 17:52 7 KB Albrecht Striffler to previous | to last
32 26-Nov-2015 17:49 7 KB Albrecht Striffler to previous | to last
31 26-Nov-2015 17:49 7 KB Albrecht Striffler to previous | to last
30 26-Nov-2015 17:40 6 KB Albrecht Striffler to previous | to last
29 26-Nov-2015 16:34 6 KB Albrecht Striffler to previous | to last
28 26-Nov-2015 16:19 5 KB Albrecht Striffler to previous | to last
27 26-Nov-2015 16:14 5 KB Albrecht Striffler to previous | to last
26 26-Nov-2015 16:13 4 KB Albrecht Striffler to previous | to last
25 26-Nov-2015 16:11 4 KB Albrecht Striffler to previous | to last
24 26-Nov-2015 16:10 5 KB Albrecht Striffler to previous | to last
23 26-Nov-2015 16:10 5 KB Albrecht Striffler to previous | to last
22 26-Nov-2015 15:33 4 KB Albrecht Striffler to previous | to last
21 26-Nov-2015 15:33 4 KB Albrecht Striffler to previous | to last

Page References

Incoming links Outgoing links
Doc TestCaseTable
Doc TestCaseTable

Version management

Difference between version and

At line 90 removed one line
At line 93 added one line
At line 96 changed one line
Using the TimeDB plugin on an api level, it is possible to set values to the session with a timestamp in the past (to represent a value being measured at a certain time being added to the session later). To represent this in the TestCaseTable markup, the column ''Time'' was extended to be able to represent a second ''insertion'' time stamp.
Using the TimeDB plugin on an api level, it is possible to set values to the session with a timestamp in the past (to represent a value being measured at a certain time being added to the session later). To represent this in the TestCaseTable markup, the column ''Time'' was extended to be able to represent a second ''insertion'' time stamp using brackets.
At line 98 added one line
It looks like this:
At line 100 added 17 lines
{{{
%%TestCaseTable
|| Time || Temperature
| 0s | 36.8
| 33min | 36.7
| 1h |
| 1h 5min (56min) | 37.8
%
}}}
In the last row, you see two time stamps. One is ''1h 5min'', the other on in brackets is ''56 min''. The semantic is, that at the session time ''1h 5 min'' the values of this row (Temperature = 37.8) will be added to the session's TimeDB with the time stamp 56 minutes. In the other rows, the timestamps at which the values are written and the timestamps with which the values are added to the TimeDB are the same.
The test case rendered in the TestCasePlayer markup would look like this (note that the columns ''Name'' and ''Checks'' are omitted in the source code example above to keep it readable):
[{Image src='TimeDBTestCase.png' width='900' height='..' style='margin-left: 20px' class='..' }]
This page (revision-34) was last changed on 26-Nov-2015 17:52 by Albrecht Striffler Top