Content deleted Content added
Reverted 1 edit by 97.77.39.130 (talk) to last revision by Walter Görlitz. (TW) |
rescued some of the anon's contents and additional |
||
Line 6:
There are various means for executing test scripts.
* [[Manual testing]].<ref>https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.rational.test.qm.doc/topics/t_construct_scripts.html&scope=null</ref><ref>{{cite web|last=Kaner |first=Cem |url=http://www.testingeducation.org/articles/fundamental_challenges_in_software_testing_presentation.pdf |title=Fundamental Challenges in Software Testing |year=2003 publisher=Florida Tech |page=35}}</ref> These are more commonly called [[test case]]s.
* [[Automated testing]].
** Short program written in a programming language used to test part of the functionality of a software system. Test scripts written as a short program can either be written using a special automated functional GUI test tool (such as [[HP QuickTest Professional]], [[SilkTest|Borland SilkTest]], [[IBM TPNS]] and [[Rational Software|Rational Robot]]) or in a well-known [[programming language]] (such as [[C++]], [[C Sharp (programming language)|C#]], [[Tcl]], [[Expect]], [[Java (programming language)|Java]], [[PHP]], [[Perl]], [[Windows Powershell|Powershell]], [[Python (programming language)|Python]], or [[Ruby programming language|Ruby]]).<ref name="undefined" /> One definition as documented in IEEE, ISO and IEC.<ref>http://www.testingstandards.co.uk/bs_7925-1.htm</ref><ref>http://www.softwaretestingstandard.org/</ref>
** Extensively parameterized short programs a.k.a. [[Data-driven testing]]
** Reusable steps created in a table a.k.a. [[Keyword-driven testing|keyword-driven]] or [[table-driven testing]].
| |||