1216329 - [convoy/testing] Implement automated network-usage tests

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Andrew Sutherland [:asuth] (he/him)]

In bug 1013373 comment 13 a user reported FxOS v1.3 email periodic sync using up ~300MB of data over 2 or 3 days for a gmail inbox with ~20 new messages per day.

While the specific circumstances of that excessive usage are likely not something that would ever recur[1], we should ensure that our correctness tests or a specific set of tests are able to provide data-points so that we can:
A) Be aware of changes in our network usage as we change the implementation.
B) Be able to easily spot unexpected regressions.
C) Be able to investigate the outcome of varying tweaks to constants.
D) Be able to identify the network fallout of pathological sync conditions.

'C' and 'D' in particular would have been very useful for analyzing the choice of bisection constants under periodic sync.  (The constants and lack of memory made sense prior to periodic sync, but arguably should have been reconsidered in the face of periodic sync.)

1: I suspect the internaldate mis-prediction issue occurred regularly and that there were a sufficient number of messages to cause bisection logic to trigger, causing spurious resyncs to occur every time periodic sync fired.  With the internaldate issue addressed, this is no longer an issue for us, and the convoy sync strategies avoid bisection issues as well.

Comment 1

[BMO Automation]

Firefox OS is not being worked on