Bartosz Dziewoński 0d23ba8bbe Fix browser tests ... Some browser tests were broken by 945fccf009. 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-19 22:27:02 +02:00
..
step_definition	Fix browser tests	2017-04-19 22:27:02 +02:00
support	Fix browser tests	2017-04-19 22:27:02 +02:00
no_javascript.feature	Fix browser tests	2017-04-19 22:27:02 +02:00
notifications.feature	Use words for describing notification counts in HTML text node	2017-03-12 19:37:23 +00:00