An initial exploration about automatic test support (T259604) concluded that it was "pretty much impossible right now to have the tests running in the CI, so we'll run them before pushing the code on our local environment".
Now that some of the workflows for Section Translation are completed we can start to define some of those automated tests. The main Section Translation epic task (T243495) can provide an overview of key workflows, but QA engineers can suggest different ones to start automating based on their experience testing them manually and [[ https://phabricator.wikimedia.org/maniphest/query/m.F5yhxnVNTY/#R | how prone these are to regressions ]].
**Additional considerations**
The future use of Vue3 may require to update the Cypress integration. However, starting to define tests now and migrating them once the new infrastructure is more solid seems to be the preferred path,
For automated tests we need to be careful on depending on real data that can change over time. For example, an article may no longer have a section present or missing. Please surface any challenges to make test defined to be solid, and we can explore how to improve the system.
** Tickets capturing key workflows**
- {T336747}
- {T295545}