Feature #12174
closedDo automated testing with Selenium
100%
Description
Recently there was an error with an implementation (#12006, fixed in #12143). This caused a JS error to be logged if a WPaintedWidget
was present on the page.
This issue could have been caught in the widget gallery, if the right page had been opened.
We can for each feature of course open each page of the widget gallery. Doing this manually for each ticket would be a waste of time. We can automate this, for example using Selenium.
While Selenium is capable of much more, and a smaller test would suffice, we can start to introduce Selenium already, so that later on more complex examples can be added.
For now it will suffice to open each page of the widget gallery, and check that no JS errors have occurred.
Later we can start doing some more integrated example, like interacting with the page by providing input, and checking its output.
Updated by Matthias Van Ceulebroeck about 1 year ago
- Status changed from InProgress to Review
- Assignee deleted (
Matthias Van Ceulebroeck)
Updated by Matthias Van Ceulebroeck 3 months ago
- Target version changed from 4.10.3 to 4.11.1
Updated by Raf Pauwels about 2 months ago
- Status changed from Review to Resolved
- Assignee changed from Raf Pauwels to Matthias Van Ceulebroeck
Updated by Matthias Van Ceulebroeck about 2 months ago
- Status changed from Resolved to Implemented @Emweb
- % Done changed from 0 to 100
Updated by Matthias Van Ceulebroeck about 1 month ago
- Status changed from Implemented @Emweb to Implemented @Test
Updated by Matthias Van Ceulebroeck 18 days ago
- Status changed from Implemented @Test to Closed