Move manifest and test handling code from CLI to Mozmill base

RESOLVED WONTFIX

Status

Testing Graveyard
Mozmill
RESOLVED WONTFIX
6 years ago
a year ago

People

(Reporter: whimboo, Unassigned)

Tracking

Details

Not sure why all the manifest handling code lives in the CLI class but that should really be in MozMill proper. Otherwise the API can be used only half-wise. I have this problem right now while working on some Python tests and I'm absolutely sure we will also face that in our automation scripts.

Was there any reason why that code has been put into the CLI class?

This is a clear blocker for us for Mozmill 2.0 because we want to always rely on manifests. Asking for blocking.
Beside manifests there is probably way more code but we should handle that on their own bugs.
Blocks: 761605
No longer blocks: 761605

Updated

6 years ago
Whiteboard: [mozmill-2.0?] → [mozmill-2.0+]
Depends on: 766113
It would be better do both (manifests and tests) at once.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Summary: Move manifest handling code from CLI to Mozmill base → Move manifest and test handling code from CLI to Mozmill base
Depends on: 767344

Updated

6 years ago
Whiteboard: [mozmill-2.0+] → [mozmill-2.1+]
Assignee: hskupin → nobody
This bug will not be taken for version 2.1. We might want to re-evaluate for 2.2.
Whiteboard: [mozmill-2.1+] → [mozmill-2.2?]
Mozmill will reach its end of life soon. We are currently working on getting all the tests for Firefox ported to Marionette. For status updates please see bug 1080766.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
Whiteboard: [mozmill-2.2?]
(Assignee)

Updated

a year ago
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.