Hey
Loli,
Im in the UK, so it's almost 4am for me too!
Regarding the first assertions when youre comparing against values already setup in an excel. Later on you compare against property values for comparison. Have you considered adding the #status# header values into properties so that rather than sometime comparing against the spreadsheet and other times comparing against values set in properties, have you considered adding in your statua header valuea into propertiea as well? This would make thinga more consistent.
I appreciate its a bit naff to just hardcode an assertion value in there rather than build the value to assert against from the environment itself (this is one o the major differences between manual test assertions and automated test assertions), but sometimes you cant do anything else.
Regarding the token value. This is one of those field values that are impossible to predict absolutely, (and so contradicts whats known as "The Oracle Assumption: all tests should have predictable value, otherwise you cant test it") so theres not much you can do with that, other than to assert its present, its not null, and perhaps has a specific character length value (or range).
Regarding the response date. You think you cant assert on it cos it always changes (and this is true in someways), however if the date that is returned is always current session datetime, you could create an assertion for the date field to equate to current date? Ive done this before....ive also done a regex assertion just to confirm the datetime values matches a specific format.
Ok. Thats it for now. Im sorry fella. I gotta get up in 3 hours.
Nice one
Rich
