BddThen class - bdd_framework_patrol library

Constructors

BddThen(BddFramework bdd, String text)

Properties

bdd → BddFramework: finalinherited
hashCode → int: The hash code for this object.
no setterinherited
runtimeType → Type: A representation of the runtime type of the object.
no setterinherited
text → String: finalinherited
variation → _Variation: finalinherited

Methods

addCode(CodeRun codeRun) → _ThenCode: Creates and registers the appropriate code term for this BDD step.
override
and(String text) → BddThen: 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) → BddThen: 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.
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: Adds a single example row to the current BDD and returns the shared BddExample block for continued chaining.
inherited
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
note(String text) → BddThen: 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: override
run([PatrolTestCallback? testCallback]) → void: Available on BddRunnable, provided by the PatrolTestRun extension
Executes the BDD scenario as a Patrol integration test.
spaces(BddConfig config) → String: override
suffix(BddConfig config) → String: override
table(String tableName, row row1, [row? row2, row? row3, row? row4]) → BddThenTable: A table must have a name and rows. The name is necessary if you want to read the values from it later (if not, just pass an empty string). Example: ctx.table('notifications').row(0).val('read') as bool.
testRun(CodeRun code, BddReporter reporter) → BddFramework
toString([BddConfig config = BddConfig._default]) → String: A string representation of this object.
override

Operators

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