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.
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.
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.
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.
This keyword is used to describe the expected outcome or result after the
'When' step is executed. It's used to assert that a certain outcome should
occur, which helps to validate whether the system behaves as expected.
An example is, "Then I should be redirected to the dashboard".
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.
