Colin_McCrae wrote:I guess it's *capable* of doing all the stuff you mention.
...
y going to be 100% cross browser compatible, out of the box, would have to be very clever, and very complex! And would likely require frequent maintenace patches to keep it in line ....
Almost the same here, but I just started it. The test runs on IE and Chrome without having to change anything but passing the browser as parameter. The only problem are the screenshots...
colin: do you use screenshots?
If yes, how do you do this?
My solution (different threat hier in the forum) works ok, but is clearly not perfect.
If you build your test correctly, most probably it can run on more than one browser.
But you sure need scripting to setting up each test and stuff.
I only use screen shots to capture whats going on at the time a script encounters errors. And even then it's kind of a debug option which I can switch on and off in the project properties as needed.
Only image compares I do are ones where I compare an image element from screen against a stored control copy. And it's always a specific image, never a full screenshot. I've always found screenshot comparison tests to be way too prone to false positives as it's so easy for them to fail. Even with a mask.
There are certain CSS instruction thats the browsers render differently. For instance, a "fade" style in a panel header was clearly visible in a panel header bar as three distinct bands of colour in IE, but was a nice gradual fade - as it's meant to be - in Chrome. Which would have caused just about any screenshot compare in the site I test to fail.
As I say, basic elements and things are generally fine cross-browser. If you start inspecting the presentation (CSS - document stylesheet) layer though, thats where you're most likey to start hitting differences.
