BddExample class
Constructors
BddExample (BddFramework bdd , val v1 , val ? v2 , val ? v3 , val ? v4 , val ? v5 , val ? v6 , val ? v7 , val ? v8 , val ? v9 , val ? v10 , val ? v11 , val ? v12 , val ? v13 , val ? v14 , val ? v15 )
Methods
example (val v1 , [val ? v2 , val ? v3 , val ? v4 , val ? v5 , val ? v6 , val ? v7 , val ? v8 , val ? v9 , val ? v10 , val ? v11 , val ? v12 , val ? v13 , val ? v14 , val ? v15 ])
→ BddExample
Examples are used in the context of Scenario Outlines. A Scenario Outline
is a template for multiple tests, and the "Examples" section provides
concrete values to be substituted into the template for each test run.
This approach allows for the specification of multiple scenarios using the
same pattern of action but with different sets of data.
formatExampleTable (BddConfig config )
→ String
Here we have something like:
{ (number;123), (password;ABC) }
{ (number;456), (password;XYZ) }
keyword (BddConfig config )
→ String
override
keywordPrefix (BddConfig config )
→ String
override
keywordSuffix (BddConfig config )
→ String
override
noSuchMethod (Invocation invocation )
→ dynamic
Invoked when a nonexistent method or property is accessed.
inherited
prefix (BddConfig config )
→ String
override
run (CodeRun ? code )
→ void
Should be used to actually provide the code that runs the BDD.
spaces (BddConfig config )
→ String
override
suffix (BddConfig config )
→ String
override
testRun (CodeRun ? code , BddReporter reporter )
→ BddFramework
toString ([BddConfig config = BddConfig._default ])
→ String
Examples have a special toString treatment.
override