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

1. Find a function and navigate to its function page
2. Go to add an implementation of the function
3. Select whether to write code (as opposed to creating a function composition)
   1. Select the required language to write the function code
   2. Get the necessary information/guidance to be able to write the function
   3. Get an blank function code snippet
   4. Get sufficient guidance on how to use the input variables?
   5. Get sufficient guidance on how to access input properties?
4. Publish my updates
   1. Visualize my implementation successfully saved
   2. IF ERROR: Visualize tester 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