transcendental-lisp/fitnesse/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteSlimTests/ScenarioTestSuite/ScriptSubclassUsedForDecisi.../content.txt

37 lines
1.4 KiB
Plaintext

Scenarios can be called from decision tables. They should respect the actor (i.e. fixture instance) and Slim table type (i.e. script table or a subclass) of the last script created.
!2 When we create a script using Slim's standard script table, the decision table should use that subtype also.
|scenario |my division1|numerator||denominator||expected|
|setNumerator |@numerator |
|setDenominator|@denominator |
|check |quotient |@expected |
Get the Division implementation from the eg package, and use a script subclass that uses 'verify' instead of the 'check' keyword.
|script|eg.Division|
|my division1 |
|numerator|denominator|expected|
|10 |2 |5.0 |
!2 When we create a script using a subclass of Slim's standard script table, the decision table should use that subtype also.
|scenario |my division2|numerator||denominator||expected|
|setNumerator |@numerator |
|setDenominator|@denominator |
|verify |quotient |@expected |
Get the Division implementation from the eg package, and use a script subclass that uses 'verify' instead of the 'check' keyword.
|verify script|eg.Division|
|my division2 |
|numerator|denominator|expected|
|10 |2 |5.0 |