mediawiki-extensions-Echo/tests/browser/features/support/pages/article_page.rb

class ArticlePage
  include PageObject

  li(:alerts, css: '#pt-notifications-alert')
  li(:notices, css: '#pt-notifications-notice')
  page_section(:alerts, Notifications, css: '#pt-notifications-alert')
  page_section(:notices, Notifications, css: '#pt-notifications-notice')
end
QA: Add some basic browser tests yippee ki yay! Tests basic functionality 1) presence of Echo button 2) behaviour of clicking Echo button Change-Id: I6334264e1ee73a59da1e7b0c3f18a1d43b565f3a 2014-08-04 23:07:37 +00:00			`class ArticlePage`
			`include PageObject`
QA: Refactoring and making the nojs test dtrt * add @custom_browser tag so we don't create an extra browser instance * remove @chrome tag because this only works in Firefox * alphabetize within G/W/T buckets in commons_steps.rb * alphabetize flyout_steps.rb * bring env.rb up to date with the modern situation * make assertions about the URL and heading on the final destination page * update Ruby gems, especially mediawiki-selenium with a @custom_browser improvement use modern RSpec assert syntax * we're going to have to update all the repos for this soon Change-Id: I6cb20126a662bd2a20e2b4bbebe91e8f3b04c7df 2014-09-22 22:00:35 +00:00
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			`li(:alerts, css: '#pt-notifications-alert')`
			`li(:notices, css: '#pt-notifications-notice')`
Browser Tests: fix * extract notifications to components/notifications.rb * wait for the flyout to be loaded before counting the unread notifications * remove popup.feature because it is redudant with notifications.feature and too low-level for acceptance testing Change-Id: If0b0286e8e98e379ae1d6d91db8084adda93b3f6 2015-11-12 17:06:11 +00:00			`page_section(:alerts, Notifications, css: '#pt-notifications-alert')`
Redo the notification badges Bug: T115845 Bug: T140900 Depends-On: Ic666540d70de52f Change-Id: I34e2736490319989a3a251a43fbe8080ab960b00 2016-07-20 00:24:17 +00:00			`page_section(:notices, Notifications, css: '#pt-notifications-notice')`
QA: Add some basic browser tests yippee ki yay! Tests basic functionality 1) presence of Echo button 2) behaviour of clicking Echo button Change-Id: I6334264e1ee73a59da1e7b0c3f18a1d43b565f3a 2014-08-04 23:07:37 +00:00			`end`