Context
We currently have a suite of end-to-end (E2E) tests that run on every patch merge request. We'd like to add test cases for the 7 critical user journeys (CUJs).
User flow
- Find a function from the Wikifunctions landing page
- Navigate to the function page
- Go to the edit page for this function
- Get a clear idea of what fields allow for modification and which fields don’t
- Modify the values of:
- Function name,
- Function aliases,
- Input list
- Add/remove input fields
- Edit input type
- Edit input labels
- Output type
- Publish my updates
- Visualize function definition successfully saved
- IF ERROR: Visualize function saving errors in a clear way for me to correct and re-save
Hints
- code location for tests: https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/WikiLambda/+/refs/heads/master/tests/selenium/
- information on Selenium testing on MediaWiki: https://www.mediawiki.org/wiki/Selenium