991485 - Provide instructions for running eideticker against 1.3

Status: RESOLVED DUPLICATE of bug 1017484

(Testing Graveyard :: Eideticker, defect)

Description

[William Lachance (:wlach)]

We should provide instructions on which gaiatest, marionette, etc. dependencies to install to use eideticker with 1.3. Ditto for 1.4 now that 1.5 is under active development. This is useful for testing things like "did this metric regress vs. the previous version".

(I'd love to be able to go back even farther than 1.3 but unfortunately eideticker depends on various functionality which was only introduced in gaiatest around version 1.3)

Comment 1

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Could we instead commit to the latest versions of eideticker, marionette, gaiatest, b2gpopulate, and any other dependencies supporting v1.3? This would make it even easier for consumers.

Comment 2

[William Hsu [:whsu]]

Thanks Will! It will be helpful because vendors are pushing Taipei office to measure the performance of V1.3, V1.4, and latest version.
As I know, GaiaUItest can automaticly pair the package version of server & client.
So, I am not sure if eideticker can do that.

Thanks.

Comment 3

[William Lachance (:wlach)]

(In reply to Dave Hunt (:davehunt) from comment #1)
> Could we instead commit to the latest versions of eideticker, marionette,
> gaiatest, b2gpopulate, and any other dependencies supporting v1.3? This
> would make it even easier for consumers.

So you mean support 1.3 via gaiatest/b2gpopulate/eideticker forever? This would be nice, but I'm not sure if it's realistic.

Comment 4

[Dave Hunt [:davehunt] [he/him] ⌚BST]

(In reply to William Lachance (:wlach) from comment #3)
> (In reply to Dave Hunt (:davehunt) from comment #1)
> > Could we instead commit to the latest versions of eideticker, marionette,
> > gaiatest, b2gpopulate, and any other dependencies supporting v1.3? This
> > would make it even easier for consumers.
> 
> So you mean support 1.3 via gaiatest/b2gpopulate/eideticker forever? This
> would be nice, but I'm not sure if it's realistic.

Maybe not forever, but support it until it's no longer needed. I think it's reasonable to set compatibility expectations for the packages, which afaik we don't currently have that beyond supporting latest/trunk.

Comment 5

[Dave Hunt [:davehunt] [he/him] ⌚BST]

This was resolved by bug 1017484 and the branched releases of the various packages.