BddGivenTable class

Inheritance

Constructors

BddGivenTable(BddFramework bdd, String tableName, row row1, [row? row2, row? row3, row? row4, row? row5, row? row6, row? row7, row? row8, row? row9, row? row10, row? row11, row? row12, row? row13, row? row14, row? row15, row? row16])

Properties

bdd BddFramework
finalinherited
hashCode int
The hash code for this object.
no setterinherited
rows List<row>
finalinherited
runtimeType Type
A representation of the runtime type of the object.
no setterinherited
tableName String
finalinherited
text String
finalinherited
variation → _Variation
finalinherited

Methods

and(String text) BddGiven
This keyword is used to extend a 'Given', 'When', or 'Then' step. It allows you to add multiple conditions or actions in the same step without having to repeat the 'Given', 'When', or 'Then' keyword. For example, "And I should see a confirmation message" could follow a 'Then' step to further specify the expected outcomes.
but(String text) BddGiven
This keyword is used similarly to "And," but it is typically used for negative conditions or to express a contrast with the previous step. It's a way to extend a "Given," "When," or "Then" step with an additional condition that contrasts with what was previously stated. For example, after a "Then" step, you might have "But I should not be logged out." This helps in creating more comprehensive scenarios by covering both what should happen and what should not happen under certain conditions.
code(CodeRun? code) → _GivenCode
formatTable(BddConfig config) String
Here we have something like: { (number;123), (password;ABC) } { (number;456), (password;XYZ) }
inherited
keyword(BddConfig config) String
inherited
keywordPrefix(BddConfig config) String
inherited
keywordSuffix(BddConfig config) String
inherited
noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
note(String text) BddGiven
Often used informally in comments within a Gherkin document to provide additional information, clarifications, or explanations about the scenario or steps. Comments in Gherkin are usually marked with a hashtag (#) and are ignored when the tests are executed. A "Note" can be useful for giving context or explaining the rationale behind a certain test scenario, making it easier for others to understand the purpose and scope of the test.
prefix(BddConfig config) String
inherited
run(CodeRun? code) → void
Should be used to actually provide the code that runs the BDD.
inherited
spaces(BddConfig config) String
inherited
suffix(BddConfig config) String
inherited
toString([BddConfig config = BddConfig._default]) String
Tables have a special toString treatment.
override
when(String text) BddWhen
This keyword indicates the specific action taken by the user or the system. It's the trigger for the behavior that you're specifying. For instance, "When I click the 'Submit' button" describes the action taken after the initial context is set by the 'Given' step.

Operators

operator ==(Object other) bool
The equality operator.
inherited