#keyword-driven testing

[name204act]

Ex.1 Trailer Test

New Post has been published on https://hollywood.newonline.help/2021/04/06/ex-1-trailer-test/

Ex.1 Trailer Test

This is a test run so I know how to use Vimeo. Full trailer coming soon. Likes: 0 Viewed: source

[testedu-blog]

Fitnesse - Keyword-driven testing

The excerpts from "Lessons learned in Software Testing" (Kaner, Bach, Pettichord) are my interpretations and not exakt transcripts. For a more exakt wording, buy the book or borrow it from your local library. It's well worth a read if you work with any kind of software testing and/or development.

Synonyms for “keyword-driven” (from MUG-keywords.pdf by Danny R. Faught) ● Action words / Action Based Testing™ (Hans Buwalda) ● Test frameworks (Linda Hayes et al.) ● Third-generation test automation (Ed Kit) ● CSDDT – Control Synchronized Data Driven Testing (Daniel Mosley) ● Test Plan Driven Testing Framework (Keith Zambelich) ● TestFrame Method (Hans Buwalda) ● TestVerb™ technology (TestQuest) ● Variable Capture / Variable Playback (Linda Hayes)

According to Lesson 128, p. 115, in "Lessons learned ..." keyword-driven test automation builds on the data-driven technique (lesson 127, a method of test automation using tables to define test input and output. The automated test procedure reads the input, executes the test and compares the output to the expected result.)

The keyword driven testing according to Kaner et al. approach expands the data-driven approach by creating task libraries that encapsulates the user tasks supported by the product. The valid start states and expected end results are linked to keywords, the keywords can then be arranged in a scriptlike order to create more advanced and complex scripts than in the data-driven approach.

Or to put it in the words of Danny R. Faught: Data-driven testing  uses a script roughly equivalent to the implementation of a single keyword. Along with the script, testers develop a list of data values that are fed to repeated invocations of the script. The difference between data-driven and keyword-driven testing is that each line of data in a keyword script includes a keyword that tells the framework what to do with the test data on that line.

Using this definition it seems like FitNesse is indeed a tool intended for or at least suitable for keyword-driven test. That it is a tool for keyword-driven testing is also explicitly mentioned in a review from 2004.

An example of it being used as such has been documented by the german tester and blogger Markus Gärtner in his post ParkCalc automation – Keyword-driven tests in FitNesse.