Test Script Design for Maximum Reusability
What are people's opinions on how to design their test scripts to make them more reusable for different testcases?
For example, for a typical web application where you log in, and then you can click on various links to navigate thru various pages, and perform various actions in each of these pages. How are people designing their scripts for such application? Right now I have each page as a separate script object, and each action as a method inside that script object. Is there any better way to do it? Or how else are people designing theirs?
Re: Test Script Design for Maximum Reusability
I think you are adopting the tarck followed by everybody.