Revision as of 20:48, 11 December 2011 edit Anandgopalkri (talk \| contribs) 9 edits No edit summary ← Previous edit		Revision as of 23:28, 11 December 2011 edit undo Walter Görlitz (talk \| contribs) Extended confirmed users, Pending changes reviewers 294,571 edits tagging. The new additions rely too heavily on a single, poor source and references that are not inline. In short I absolutely hate the project oversight by the India Education Program as the output is usually bad, and this is of acceptable quality. Next edit →
Line 1: {{Multiple issues ~~{{Cleanup~~\|~~date~~ cleanup = December 2007}} \| unreliable sources = December 2011 \| refimprove = December 2011 \| no footnotes = December 2011 }} A '''test automation framework''' is a set of assumptions, concepts and tools that provide support for [[test automation\|automated software testing]]. The main advantage of such a framework is the low cost for maintenance. If there is change to any test case then only the test case file needs to be updated and the [[Driver Script]] and [[Startup script]] will remain the same. Ideally, there is no need to update the scripts in case of changes to the application. Line 42 ⟶ 47: * Interface Environment * Object Repository ==Interface engine== Line 55 ⟶ 59: ==References== {{Reflist\|3}} * Hayes, Linda G., "Automated Testing Handbook", Software Testing Institute, 2nd Edition, March 2004 * Kaner, Cem , "[http://www.kaner.com/pdfs/testarch.pdf Architectures of Test Automation]", August 2000

Test automation framework: Difference between revisions