Make url parameter optional in seePageIsAvailable
#114
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have been monitoring the use of this method in the public repositories that use this module.
I'm glad to see that it quickly became a very popular assertion. This is mainly because it is more natural to talk about available pages than 2xx response codes.
However, I have seen that in many cases
amOnPageis used as a previous step, perhaps because it is more natural to read them separately. To avoid redundancies, the$urlparameter will be optional, so both ways (the current one with a parameter, and the new one, without it) will be valid no matter which one you choose to use.