Skip to content
This repository was archived by the owner on Oct 14, 2025. It is now read-only.

Conversation

@kdimopulu
Copy link
Collaborator

No description provided.

@kdimopulu kdimopulu marked this pull request as draft October 23, 2024 09:01
@blacksmith-welder blacksmith-welder changed the title Accession Accession Spawn feature Accession Spawn feature Oct 23, 2024
@blacksmith-welder blacksmith-welder force-pushed the accession_accession_spawn_feature branch from ef12429 to 20237f4 Compare October 25, 2024 13:37
@kdimopulu kdimopulu marked this pull request as ready for review October 25, 2024 13:51
Copy link
Collaborator

@balmas balmas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. A couple of minor changes suggested.

expect(page).to have_field(label, checked: true)
end

Then 'the following error message is displayed' do |messages|
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe consider renaming to 'only the following error message is displayed' since that's what distinguishes this method from the prior one which also tests for a message being displayed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that it is more distinguishable that way. I have prepended the word only to all the steps that refer to a single message, as well as a check that there is only one message wherever it was missing.

Some notes, which also apply to the other reviews (16)

@kdimopulu suggested the same thing before submitting for review, but I thought that since the distinction is already there (plural/singular), it's redundant to prepend the word only, to make it as simple and intuitive as possible for the Gherkin writer, without having to search other steps or referring to the documentation.

From the technical point of view, the error/info messages can always be an arbitrary amount of entries in Gherkin/Cucumber, so we could even use the plural version for everything, to make it even simpler.

eg.: Somebody could write the following for a single message, which is totally valid:

Given ...
When ...
Then the following error messages are displayed
  | Expression - is required unless a begin or end date is given |
Then ...

expect(find('.alert.alert-success.with-hide-alert').text).to match(/^#{string}.*updated$/i)
end

Then('the following info message is displayed') do |messages|
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/b 'the following info messages are displayed' because it accepts and tests multiple

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed. There is a check for messages length now.

@balmas balmas mentioned this pull request Oct 28, 2024
Copy link
Collaborator

@brianzelip brianzelip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏼

@blacksmith-welder blacksmith-welder force-pushed the accession_accession_spawn_feature branch 4 times, most recently from faf13d9 to 1c04ca1 Compare November 13, 2024 17:46
@blacksmith-welder blacksmith-welder changed the title Accession Spawn feature Accession spawn Accession Nov 13, 2024
@blacksmith-welder blacksmith-welder force-pushed the accession_accession_spawn_feature branch from a7ee499 to 70b6d9a Compare November 14, 2024 09:58
@blacksmith-welder blacksmith-welder merged commit bd83a84 into master Nov 14, 2024
1 check passed
@blacksmith-welder blacksmith-welder deleted the accession_accession_spawn_feature branch December 21, 2024 07:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants