You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there are times when you require to expand the context, if you feel a need to type 'and' in the context of a GIVEN, WHEN, and/or THEN, you should use AND.
we don't have an AND, because that just doesn't work in this abstraction; thus we have AND_WHEN and AND_THEN; thus we should also have AND_GIVEN.
The text was updated successfully, but these errors were encountered:
issue #1360
It is possible to have multple given contexts in a single BDD scenario;
if you have to type 'and' in the GIVEN description; it's very likely you
need an AND.
A generic AND is not possible, thus a AND_GIVEN is added to complement
the AND_WHEN and AND_THEN.
Can be used without needing to increase indent:
SCENARIO("...") {
GIVEN("...")
AND_GIVEN("...") {
WHEN("...") {
THEN("...") {
// ...
}
}
}
}
would correctly output, when requested/needed:
Given: ...
And given: ...
When: ...
Then: ...
The padding had to be increased by a character in the output message, to
continue to be uniform.
To be consistent with the
AND_WHEN
andAND_THEN
;With BDD:
there are times when you require to expand the context, if you feel a need to type 'and' in the context of a
GIVEN
,WHEN
, and/orTHEN
, you should useAND
.we don't have an
AND
, because that just doesn't work in this abstraction; thus we haveAND_WHEN
andAND_THEN
; thus we should also haveAND_GIVEN
.The text was updated successfully, but these errors were encountered: