Page MenuHomePhabricator

Document Test Platforms responsibility for browser test frameworks to make public what we do and do not do
Closed, ResolvedPublic3 Estimated Story Points

Description

Lets write down our responsibility for the browser tests framework(s) so it's easy for us to:

  • Know if an issue is our responsibility or not
  • Easy for managers to route issues to the correct people

For now, let's focus on what we actually do and not what we would like to do.

AC:

Event Timeline

zeljkofilipin added a subscriber: Peter.

@Peter do you have an example page for some other framework?

Peter renamed this task from Document QTE responsibility for Selenium framework to Document Test Platforms responsibility for Selenium framework.Jan 22 2025, 12:04 PM
Peter renamed this task from Document Test Platforms responsibility for Selenium framework to Document Test Platforms responsibility for browser test frameworks to make public what we do and do not do.Sep 8 2025, 2:58 PM
Peter updated the task description. (Show Details)
zeljkofilipin changed the task status from Open to In Progress.Sep 12 2025, 8:54 AM
zeljkofilipin triaged this task as High priority.
zeljkofilipin moved this task from Backlog to In Progress on the Test Platform (dek tri 13) board.

Subscribing to this because it's going to be a very useful document for my team.

@SLong-WMF The document is pretty much done, at least the first version of it. I'm looking for feedback from my team, but also from people outside the team. Feel free to leave comments and questions in the document. I'm also open to talking about it in a meeting, if that would be useful.