* removed wait_until where possible * replaced wait_until with DOM obersavtions * added match: :first to all finders that assumed getting the first element * replaced evaluate_script with execute_script where possible * replaced a few execute_script with DOM observations through Capybara * removed sleep where possible * replaced sleep with DOM obersvations * replaced "wait for ajax" with DOM obersavations * replaced alert confirmation with new selenium API * bump selenium webdriver * made any other fixes to get green again
26 lines
853 B
Gherkin
26 lines
853 B
Gherkin
@javascript
|
|
Feature: Blocking a user from the stream
|
|
Background:
|
|
Given following users exist:
|
|
| username | email |
|
|
| Bob Jones | bob@bob.bob |
|
|
| Alice Smith | alice@alice.alice |
|
|
And a user with email "bob@bob.bob" is connected with "alice@alice.alice"
|
|
And Alice has a post mentioning Bob
|
|
And I sign in as "bob@bob.bob"
|
|
|
|
|
|
Scenario: Blocking a user
|
|
When I am on the home page
|
|
When I click on the first block button
|
|
And I confirm the alert
|
|
And I am on the home page
|
|
Then I should not see any posts in my stream
|
|
|
|
Scenario: Blocking a user from the profile page
|
|
When I am on the home page
|
|
And I follow "Alice Smith"
|
|
When I click on the first block button
|
|
And I confirm the alert
|
|
And I am on the home page
|
|
Then I should not see any posts in my stream
|