database checkpoints - masking expected results ???
User zol_city (email@example.com) posted:
i am doing database checkpoints on tables containing date fields and
the problem is that everytime i run the test most of the dates are
updated with the current date, and this causes mismatches everytime.
i do not want to exclude those date fields from my sql statement
because there are times that i need to check some of the expected
dates (ie. there dates are != current date).
is there a way of masking some of the expected values so that the
data checkpoint will ignore those values.