You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to assert that a result-set, with a time period, is including/leading/lagging a given datetime. A time period is defined as the closed-open time interval between two datetime.
For lags and leads, it's possible to define a variant immediately="true" to specify that the time-period should starts/ends at the given date.
The optional group-by let you define that system-under-test rows should not be tested as a single set of rows but should be subdivided into subsets, each subset being defined by the group-by.
The text was updated successfully, but these errors were encountered:
Seddryck
changed the title
Support temporal assertions for a time period and a given date/time
Support temporal assertions regarding intersection of a time period and a given date/time
Aug 5, 2022
Seddryck
changed the title
Support temporal assertions regarding intersection of a time period and a given date/time
Support temporal assertions regarding intersection of a time period and a given datetime
Aug 5, 2022
It should be possible to assert that a result-set, with a time period, is including/leading/lagging a given datetime. A time period is defined as the closed-open time interval between two datetime.
For lags and leads, it's possible to define a variant
immediately="true"
to specify that the time-period should starts/ends at the given date.The optional
group-by
let you define that system-under-test rows should not be tested as a single set of rows but should be subdivided into subsets, each subset being defined by the group-by.The text was updated successfully, but these errors were encountered: