Page MenuHomePhabricator

[EPIC] Define and document the process to test our design system with users
Closed, ResolvedPublic

Description

Background/Goal

We need to define the process to test our system components with real users.

User stories

  • As a system designer, DST member or external contributor, I need to know the process to test system components.
  • As a system designer, DST member or external contributor, I need to know when should I test a component.

Open questions

  • Goals to test our system components
  • What type of components do we want to test and why (e.g. Fullscreen Dialog)
  • Which tools are we going to use
  • Who will be the owner of each component's user testing?

Documentation


Acceptance criteria (or Done)


Future tasks

Event Timeline

I would revise this task acceptance criteria to be about creating a first draft process for testing components, and then evaluate how well it works in a pilot component test before making changes and then adding it to system guidelines.

Yeah, the system resources updates would be a reasonable deliverable for this epic task, with everything else leading up to it being broken into subtasks - if we're confident that it can all be completed in ~3 months.

bmartinezcalvo renamed this task from [EPIC] Define and document the process to test our components with users to [EPIC] Define and document the process to test our design system elements with users.Jan 9 2024, 5:35 PM
bmartinezcalvo renamed this task from [EPIC] Define and document the process to test our design system elements with users to [EPIC] Define and document the process to test our design system with users.Jan 9 2024, 5:37 PM
bmartinezcalvo updated the task description. (Show Details)
bmartinezcalvo updated the task description. (Show Details)
bmartinezcalvo claimed this task.
bmartinezcalvo updated the task description. (Show Details)

@CCiufo-WMF solving this Epic since all its subtasks have been completed.