Anyone heard of an object model in automated testing. What information is it supposed to convey, and what essentially should be its structure i.e. to how much detail should one dwelve. What approach should one consider - objects by use case? or objects by functionality ...

Any help would be highly appreciated.

Kashif Choudhry,
Lead, Automated Testing - Vroom Technologies Inc.