Boundary parameter in Feature context

[hub20xx]

Hello there,

first of all, thank you so much for the clean and practical example of EBI. I'm a newbie and it helps me tremendously to get started by looking at how you built this douche app :)

I have a question regarding the use of the boundary parameter in the behat.yml and in the FeatureContext, while loading the helpers.

From my newbie point of view, it seems like when the end-to-end profile is run, then the boundary is always http and not app, so I don't get why checking both for the tag @end-to-end-available and for the value of boundary.

Why not checking only (simply) for the tag?

[davedevelopment]

@hub20xx been a while since I wrote that, but I think not all tests have end-to-end steps written, so when the end-to-end profile is run, it's kind of like setting the preferred boundary to http. The conditional is then doing "if they have said they would prefer http and the current scenario supports end to end, use http".

[hub20xx]

@davedevelopment Thank you for your feedback. Yes it's been a while ;) I guess my question came from the observation, that the end to end behat profile has always the boundary set to http and always uses the @end-to-end-available tag, so it looks like checking both was kind of redundant. I could not see the use of the boundary parameter elsewhere so I was wondering if I was missing something.

[davedevelopment]

Ah sorry, I see what you mean. Yes, looking at it, that check is redundant with the profiles in the setting file, but I guess I wrote it thinking it may be a possibility? I don't know :)

[hub20xx]

Thank you for your answer. I wanted to make sure I was not missing something else. :)

I'm using your code to build a small app based on EBI and I'm learning so much from reading and following the code of this doucheapp.

Thank you very much for sharing it!