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 a given time-period. A time period is defined as the closed-open time interval between two datetime.
The including assertion should validate if the reference period is fully covered by the time-period defined in the result-set.
The intersects assertion should validate if the reference period and the time-period defined in the result-set are overlaping at least a moment.
The leads assertions should validate if the reference period is starting after the time-period defined in the result-set.
The lags assertions should validate if the reference period is starting after the time-period defined in the result-set.
For lags and leads, it's possible to define a variant strictly="true" to specify that there should be no intersection, meaning that the end-date should be prior to the start-date. As we've closed-open intervals, if the start date and end date are represented by the same value they automatically don't intersect.
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 regarding a time period containing a specific time period
Support temporal assertions regarding a time period overlaping/intersecting a specific time period
Aug 6, 2022
Seddryck
changed the title
Support temporal assertions regarding a time period overlaping/intersecting a specific time period
Support temporal assertions regarding a time period including/intersecting a specific time period
Aug 6, 2022
It should be possible to assert that a result-set, with a time period, is including a given time-period. 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
strictly="true"
to specify that there should be no intersection, meaning that the end-date should be prior to the start-date. As we've closed-open intervals, if the start date and end date are represented by the same value they automatically don't intersect.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: