Yeah that's the idea...
The testing framework should log the progress of the test script, including
successful and unsuccessful steps. For example, if the statement
click({element:'#link1'}); does not find a link with the specified id, it
will croak to the log and stop the script. Similarly if
wait_till_loaded({element:'#div1',timeout:3000}); does not find the element
before timeout, the same will be logged.
This would surely catch missing links or missing elements that need to be
present. But I dont know about formatting... that's a visual aspect that may
be difficult to measure... but one could still measure the location of
various elements using the DOM... so maybe simple formatting tests could
also be created.
To begin with, I'd like to use something like this to validate a series of
standard unit tests every time we are ready to check out a new version on
the live site... which happens practically every day... and I do not see
that pace decreasing. If we are serious about web2.0 leading to enterprise
2.0, and expect that iterative development (
http://www.on2.biz/2006/11/22/on2biz-iterative-development/) is used for
mainstream web apps, we will need tools like this for sure.
On 12/5/06, bmsterling <[EMAIL PROTECTED]> wrote:
That actually sounds quite interesting, is the point to test for errors?
Missed links? Formatting errors? If so, there should be a way to send
those errors to the parent frame and then with serverside scripting, send
an
email or input those errors into a db to create a punchlist of sorts.
--
View this message in context:
http://www.nabble.com/Web-application---site-testing-framework-using-jquery--tf2763160.html#a7704358
Sent from the JQuery mailing list archive at Nabble.com.
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
--
Reach1to1 Communications
http://www.reach1to1.com
[EMAIL PROTECTED]
98201-94408
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
