Add options to Steeplechase to keep existing profile on the Negatus client, if it exists

NEW
Assigned to

Status

4 years ago
8 months ago

People

(Reporter: martijn.martijn, Assigned: martijn.martijn)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

4 years ago
Pushing the client binaries to the Negatus clients can take quite some time (couple of minutes).
Often, when the Steeplechase tests were run before, the old binaries are still there on the Negatus machines and could be used, instead.
Same for the profile directories.
We could add options like --keep-binary and keep-profile to runsteeplechase.py
for this.
There's --noSetup, which will skip pushing the app, but I didn't add a way to skip pushing the profile. Currently the profile contains things like the URL to the signalling server, although that's not likely to change between runs anyway, so we could definitely reuse the profile. It wouldn't be hard to make --noSetup skip pushing the profile as well.

Comment 2

4 years ago
--no-setup will still push the profile? That's perfect, actually. It would still be good to be able to skip the profile push, but for WebRTC, we need to push the profile every time, since the port number given to us by the signaling server is random.

Sounds like there is no immediate work necessary here.
(Assignee)

Comment 3

4 years ago
Doh! runsteeplechase.py --help would have told me this.
(Assignee)

Updated

4 years ago
Summary: Add options to Steeplechase to keep existing profile/binary on the Negatus client, if it exists → Add options to Steeplechase to keep existing profile on the Negatus client, if it exists
Component: New Frameworks → General
Product: Testing → Testing
You need to log in before you can comment on or make changes to this bug.