Revision as of 09:11, 27 November 2007 edit Nalinnew (talk \| contribs) 1 edit →Frameworks ← Previous edit		Revision as of 22:06, 22 December 2007 edit undo Iridescent (talk \| contribs) Administrators 402,821 edits m Cleanup & typo fixing , typos fixed: upto → up to using AWB Next edit →
Line 1: {{cleanup\|date=December 2007}} A '''Test Automation Framework''' is a set of assumptions, concepts and practices that provide support for [[test automation\|automated software testing]]. Line 9 ⟶ 10: Frame work means a set of rules developed by experts and using by many people. Will Automation testing beats Manual? The debate should be how to bridge the gap between automation and manual testing.....! At one point these two streams start interdepending and the ideal problem is how to eliviate automation testing ~~upto~~up to manual testing in some aspects and how to uplift manual testing to automation testing level in few other aspects. == External links == * [http://www-128.ibm.com/developerworks/rational/library/05/1011_kelly Modularity Framework]<br /> * [http://www-128.ibm.com/developerworks/rational/library/05/1108_kelly/ Data-driven Framework]<br /> * [http://www-128.ibm.com/developerworks/rational/library/06/0523_kelly/ Keyword-driven Framework]<br /> * [http://qtp.blogspot.com/2007/06/choosing-test-automation-framework.html Choose an Automation Framework] [[Category:Software testing]] [[Category:Automation]]

Test automation framework: Difference between revisions