Critical User Journey 1: Evaluate a function

Job To Be Done

When <situation> I want to <job> so I can <expected outcome or motivation>

Acceptance criteria

Any user...

• Should be able to find a function from the Wikifunctions landing page
• Should be able to navigate to the function page
• Should be able to select or write any valid input values
• Should be able to understand what input values are valid and which ones are not
• Should be able to run the function and see the output generated with my input values
• Should be able to understand what went wrong in case the function evaluation failed

Completion checklist

During the review process, edit and check these items to reflect the completion status of this epic

• Functionality
  • Every project (repository) involved in this user story has its separate Phabricator task
  • Every related task should passes its completion checklist
  • The tests for every involved project pass successfully
  • The build process for every involved project passes successfully
  • Coverage for every involved project has improved or stayed the same
• Design
  • Design review on updated software
  • Test concept via an Alpha, Beta or Prototype with partner communities and those potentially impacted by feature, in their preferred language
• Documentation
  • Has related and updated documentation, E.g.:
    • Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc)
    • Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on MediaWiki extension pages.
    • Product or model changes: should have related documentation updated in meta
• Versioning
  • If changes in submodule packages are involved, every project that uses this submodule has updated submodule version and passes tests and build