Hi,
I haven't used myself (_yet_), so not sure if it'll meet all you require, but have you looked at Webaii? http://www.artoftest.com/support/webaii/topicsindex.aspx Looks it could fit to what you describe. HTH. Cheers, Brian. From: [email protected] [mailto:[email protected]] On Behalf Of Steven Nagy Sent: Monday, 1 February 2010 11:55 AM To: ozTFS Subject: Coded UI Tests Hi all, We use TFS2010 with the full lab management bit, running coded UI tests as part of the nightly build. One of the things I've found is that the VS coded UI tests replicate large chunks of the page in code. For example, it creates classes for the DOM, window, divs, tables, etc. These are all strongly typed classes that represent your exact div or table. We're finding this kind of structure very inflexible. Typically an assertion might only care that the date on the screen is valid, not where it sits in the structure of the page. When the UI guys get their hands on a page and change things around, even slight changes cause a bunch of tests to fail. Even changing the title of the page has drastic consequences! We're looking at using WatiN instead (watin.sourceforge.net) because it lets you just ask for a control by name or id. This means we can find anything we want to validate, click, or enter text for, without having to care where on the page it is. But before we dive down this route, is this something that the existing coded UI tests will let us do? I can't see how but that doesn't mean its not there. Our app is very flexible and the UI constantly changes. This shouldn't mean we have to defer testing until the very end. Appreciate any tips or advice on proceeding with the OOTB tooling. Steven Nagy Readify | Senior Developer M: +61 404 044 513 | E: <sip:[email protected]> [email protected] | B: <http://azure.snagy.name/> azure.snagy.name
_______________________________________________ oztfs mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/oztfs
