web-platform-tests / web-platform-tests/rfcs

Hardware and Testing capabilities for mobile environments

Open
#126 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
110
Forks
90
PR merge metrics
No merged PRs in 30d

Description

Hi https://github.com/orgs/web-platform-tests/teams/wpt-core-team!

(This is related to a discussion started by @jgraham in https://github.com/web-platform-tests/interop-2022-viewport/issues/23#issuecomment-1273448590 related to viewport testing)

Context

The availability of appropriate hardware for testing on mobile is key to be able to get meaningful results for some areas such as viewport. If the WPT project wants to explore further, there exist a number of issues.

Issues

  • The current hardware setup (taskcluster or Azure) doesn't make it possible to test properly for viewport tests.
  • Android and iOS have different hardware and infrastructure requirements.
  • What would be the yearly budget for these infrastructures? (Ballpark)
  • Are there other blockers, or at least difficulties to identify ?
  • Would it be possible to gain resources and/or budgets to be able to run these tests.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked viewport discussion and the current Taskcluster and Azure hardware setup. Document the Android and iOS requirements, infrastructure blockers, estimated yearly budget, and possible funding or resource sources. Done means the mobile testing requirements and next steps are clearly identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, azure, ios
Domain
cloud, infrastructure, mobile, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.