It is worth mentioning that there are pros and cons to each approach. In some ways,
WebDriver is exactly the right tool for this job.
In the PRO column using WebDriver:
- the ability to check links that are created dynamically by JS and don't appear in the page
source. This is _really_ difficult without a real browser or making assumptions about the
the page construction
- following links that implemented via an onClick() method (see above)
In the CON column:
- harder to check for "page not found" (404s) without access to the HTTP status code - the
solution may need to be browser specific.
> --
> You received this message because you are subscribed to the Google Groups "webdriver" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
>
webdriver+...@googlegroups.com <mailto:
webdriver+...@googlegroups.com>.
> To post to this group, send email to
webd...@googlegroups.com <mailto:
webd...@googlegroups.com>.
> Visit this group at
http://groups.google.com/group/webdriver.
> For more options, visit
https://groups.google.com/groups/opt_out.
--
------------------------------------------------------------------------ -
Chris Merrill | Web Performance, Inc.
ch...@webperformance.com |
http://webperformance.com
919-433-1762 |
919-845-7601
Web Performance: Website Load Testing Software & Services
------------------------------------------------------------------------ -