Hi,
I've several problems with current compareToExpected step:
- name doesn't fit with all our verifyXXX steps
- if reference file doesn't exist, it looks silently for it in a
subfolder named "expected"
- it doesn't fail if reference file doesn't exist at all but just creates it
- it doesn't fail if an IO error occurs
Therefore I propose to deprecate compareToExpected and to introduce a
verifyContent which would offer the same functionalities as
compareToExpected but in a more deterministic way. This would look like:
<verifyContent referenceFile="someFile.xxx".../>
Any thoughts?
Marc.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
