Hey AAB
dunno whether I can help - but I'm responding cos no-one else has yet.
im a bit lost on this one cos Im not understanding what the problem is - it feels fairly straightforward (and normally your questions are a lot more difficult to answer) which leads me to believe Im really not understanding!
the way I read this is that you have had a new build of code and the date attribute value has altered and you want to assert that it is 31/12/2019 rather than 31/12/2018 - cos that seems straightforward - just use a contains or not contains assertion.
as I say above - normally your questions make me think - so I must not be understanding what the problem is....????
cheers,
rich
Hello Richie,
Thanks for your time and answer.
It is almost straightforeward but not completely. As I don't know when the new update will be, the assertion needs to notice this on it's own. I don't know per definition if every update from third party will be at the end of the year. It could be in July or January for that matter. This was just a first step for me to maybe be able to find something suitable for my case. This was actually an example. I had some thoughts to find it like in the 'SetupScript' for a check if that day has changed. If yes, continue all the automated tests. if the date hasn't change, don't execute the tests.... or something like that.
Cheers!
