Cloud: Sauce Labs upload omits the documented `name` form field

Open
#436 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
dart, go
Domain
mobile, testing

Research direction

Find the Sauce Labs upload code that sends the payload form field and inspect the Appium capabilities code that uses storage:<id>. Start by tracing the upload flow and its existing tests; the issue does not name files or confirm whether name is required. Confirm the live API behavior, add the field and an httptest form-field check if required, and verify how the uploaded file is referenced in capabilities.

Written by the indexing model from the issue text.

Description

area/cloud bug

The Storage API page lists the form fields payload (the file) and name (the filename with extension), plus optional description, tags and project_name (https://docs.saucelabs.com/dev/api/storage/, read 2026-10-14). Our upload sends payload only.

Acceptance criteria

  • Confirm on a live account whether name is required.
  • Send it if so, with an httptest form-field test. Also verify how an uploaded file is referenced in the Appium capabilities (the code uses storage:<id>; the page read did not show it).
Dominant language
Go
Stars
6
Forks
3
Avg merge
6h 28m
Merged PRs (30d)
362

Getting set up

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.

More from AlphaWaveSystems/flutter-probe

All issues in AlphaWaveSystems/flutter-probe

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.