In T158074, @zeljkofilipin upgraded the majority of extensions with automated browser tests were upgraded to Selenium without a snag. However, there were issues while upgrading the RelatedArticles extensions.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | zeljkofilipin | T157695 Selenium tests broken on Ruby 2.4 | |||
| Declined | None | T158074 Update Ruby tests to Selenium 3 | |||
| Resolved | Jdlrobson | T162936 Improve developer happiness in reading web maintained extensions | |||
| Duplicate | None | T160359 Upgrade RelatedArticles automated browser tests to Selenium 3 |
Event Timeline
Comment Actions
@zeljkofilipin If we migrate to Selenium node browser tests instead does that make this task redundant?
Comment Actions
Correct. If you reimplement tests in nodejs, there is no need to keep ruby tests around, or spend any time updating them.