mediawiki-extensions-Echo/tests/browser/features/step_definition/badge_steps.rb

# Steps related to clicking and interacting with the badge
# Work in both nojs and js version

Given(/^I click the alert badge$/) do
  on(ArticlePage).alerts_element.when_present.click
end

Given(/^I click the notice badge$/) do
  on(ArticlePage).notices_element.when_present.click
end
Rewrite browser tests for Echo The new oouified echo popup makes the tests invalid; this commit rewrites those tests. Also by doing this commit we are upgrading to Selenium 1.4. Change-Id: I26215558768d55be449276c55b4b745c3a458ecb 2015-09-25 21:17:54 +00:00			`# Steps related to clicking and interacting with the badge`
			`# Work in both nojs and js version`

			`Given(/^I click the alert badge$/) do`
Fix browser tests Some browser tests were broken by 945fccf0099058eeed4d318a27acbe193739f64e. The badge element is now technically rendered offscreen, with only the :before and :after pseudoelements being onscreen. Because of this, Selenium thinks that the badges are invisible, and this breaks various things in totally unexpected ways. * article_page.rb: Store references to the parent <li> elements of badges. This might not be necessary but I don't know how to access them otherwise. * badge_steps.rb: When clicking the badges, click the parent <li> element rather than the not-really-invisible <a>. Effectively, the <a> gets clicked anyway, since they overlap. * no_javascript.feature/no_javascript.rb: Wait for page load before checking that we're on the right page. The wait is no longer implicit, since Selenium thinks we're clicking the <li> rather than <a> (links are special-cased). * notification_steps.rb: * Check whether the badges exist on the page, rather than whether they are visible. * Use a weird hack to read badge text. Apparently you can't read the text of elements that Selenium thinks are invisible. http://stackoverflow.com/questions/20888592/gettext-method-of-selenium-chrome-driver-sometimes-returns-an-empty-string Bug: T161941 Change-Id: Ic6bcd1088249109e49a47cc9007e6ee002d3d8ba 2017-04-13 00:47:17 +00:00			`on(ArticlePage).alerts_element.when_present.click`
Rewrite browser tests for Echo The new oouified echo popup makes the tests invalid; this commit rewrites those tests. Also by doing this commit we are upgrading to Selenium 1.4. Change-Id: I26215558768d55be449276c55b4b745c3a458ecb 2015-09-25 21:17:54 +00:00			`end`
Add browser test for notifications in Echo This browser test checks that mentions go to alerts and talk page messages go to messages popup. This also upgrades the MW-Selenium version in Echo tests to 1.6.1. Depends on MW-Selenium version 1.6.1 (See T114061) Bug: T113081 Change-Id: I40a17500cdfb838420c04dc0b9268ba56515cc2c 2015-09-29 00:07:37 +00:00
Redo the notification badges Bug: T115845 Bug: T140900 Depends-On: Ic666540d70de52f Change-Id: I34e2736490319989a3a251a43fbe8080ab960b00 2016-07-20 00:24:17 +00:00			`Given(/^I click the notice badge$/) do`
Fix browser tests Some browser tests were broken by 945fccf0099058eeed4d318a27acbe193739f64e. The badge element is now technically rendered offscreen, with only the :before and :after pseudoelements being onscreen. Because of this, Selenium thinks that the badges are invisible, and this breaks various things in totally unexpected ways. * article_page.rb: Store references to the parent <li> elements of badges. This might not be necessary but I don't know how to access them otherwise. * badge_steps.rb: When clicking the badges, click the parent <li> element rather than the not-really-invisible <a>. Effectively, the <a> gets clicked anyway, since they overlap. * no_javascript.feature/no_javascript.rb: Wait for page load before checking that we're on the right page. The wait is no longer implicit, since Selenium thinks we're clicking the <li> rather than <a> (links are special-cased). * notification_steps.rb: * Check whether the badges exist on the page, rather than whether they are visible. * Use a weird hack to read badge text. Apparently you can't read the text of elements that Selenium thinks are invisible. http://stackoverflow.com/questions/20888592/gettext-method-of-selenium-chrome-driver-sometimes-returns-an-empty-string Bug: T161941 Change-Id: Ic6bcd1088249109e49a47cc9007e6ee002d3d8ba 2017-04-13 00:47:17 +00:00			`on(ArticlePage).notices_element.when_present.click`
Add browser test for notifications in Echo This browser test checks that mentions go to alerts and talk page messages go to messages popup. This also upgrades the MW-Selenium version in Echo tests to 1.6.1. Depends on MW-Selenium version 1.6.1 (See T114061) Bug: T113081 Change-Id: I40a17500cdfb838420c04dc0b9268ba56515cc2c 2015-09-29 00:07:37 +00:00			`end`