can i know whats wrong u had before with robot built-in vp.
it seems like ok to me.
it really shorten the codes to verify thing like data,property image...
we can customize a bit on the built-in vp, thus i think it is till highly usable.
furthermore i haven't tried to verify those data content inside an object by using sqagetproperty. interesting to me too.
You are very limited when using built in VPs. You can actually write your own using SQAGetProerty etc... and functionalize them and make them much more powerful.
Ex1: Say you make an object data vp. then next time you run your script it can fail because of changes such as date, time, text, upper/lower case, unique ID number, sort order, etc...
Ex2: If you use an object data vp with one backend database, then decide to use your scripts on another database, everything will fail since all the data is now incorrect. This makes doing any sort of datdriven testing (i.e. injecting test data from a spreadsheet or test DB) impossible.
Ex3: If you ever want to copy, share, version control your scripts you have a lot of baggage that Robot generates when using VPs. If you "roll your own" it's all in .REC .SBH and .SBL files only.
For an Object VP to succeed you need 100% of the recorded data to be the same each and every time you run your scripts.
If you write your own verifications you can specify what needs to match, what is allowed to be different, etc... Sometimes it is ok (and mandatory) for data to be different than the last run of the scripts.
Did that make any sense at all to you?
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!