Try using the Verification page while recording. You can select the objects and properties of those objects that you want to verify. Or you can use the Verify function and create a similar thing yourself. For some things in the HTML page that aren't visible you may have to have the script read the source of the page and verify further things that way.
Yup, I agree with Shree.. I advocate using Verify function only for specific properties, not to verify the whole content or n^n properties... Like the one that is recorded by the TestCase recording wizard for Window Verification.
Automation should start only after the GUI is stable enough. Before this stage Manual verification would be faster, and once these bugs get fixed the likelyhoood of regression for GUI props in pretty low.
// The Persistent Bugger
It's all true if you are testing on one OS and one language.
If you test on multiple OS and language UI automation is still very worthwhile (it depends how well you can abstract the localized strings). It depends what are the requirements. UI mapping is a pain (overhead and maintenance) that we all agree no matter if it's worthwhile or not [img]images/icons/smile.gif[/img]
A lot of people in here have tested a web site before.
Have you done any testing with SilkTest on your portal yet? Do you have a problem you want to discuss?
SilkTest can do web site (or portal) testing.
You should start trying something (it takes 5 min to find out if SilkTest is up to the task). If you don't even have SilkTest at hand then it's gonna be hard to speculate what it can do or not for you.