|Open||None||T113249 [WMDE-Fundraising] Epic: Rewrite of frontend|
|Resolved||gabriel-wmde||T155016 Donation/Membership address form submit fails when button is clicked|
|Resolved||None||T123053 [WMDE-Fundraising] Browser tests for system-level tests|
|Resolved||gabriel-wmde||T123050 [WMDE-Fundraising] Prepare server configuration and deployment scripts|
|Open||None||T147941 Browser tests for notices|
Are these tests currently being run automatically anywhere? Are they maintained and all passing for the old app? Who is responsible for updating them, and when does that happen?
Is it likely to be hard to modify the tests to work with the new app due to the fronted changes we made?
As we have a lot of edge-to-edge tests in the new app anyway, browser tests don't seem that critical. Though it would still be nice to have a few testing the most important things. Creating and maintaing them and the infrastructure they run on might be a lot of work tho...
To answer the questions of @JeroenDeDauw:
They aren't run automatically at the moment.
For the old app they were passing, but that's moot since we'll kill the old app.
We (the FUN team) are responsible for the tests. I'd suggest we update the tests and add new ones when there is a new feature.
Most of the tests ran well with the new application. Updating the tests was mostly about, add new defaults (the old application had an amount default) and changing some CSS selectors or adding classes to templates to restore the selectors. There were some weird JS issues that came from async behavior that needed to be fixed.
As we've seen, the browsers tests would have saved us lots of trouble because our "edge-to-edge" test only test the "PHP backend" behavior and not the interaction between templates, client-side JS and PHP backend. So maintenance of the browsers tests - especially when we're updating the HTML this year - is important.