On 9/08/2016 07:52, Karl Thiessen wrote: > TPS was originally conceived as a method of testing the Sync > client code that lives in Firefox against "known-good" Sync server, i.e. > the production Sync cluster. But I know of no reason why it could not > be used the other way around, to test new changes to the Sync server > with "known-good" (i.e. released) Firefox clients, potentially both > desktop and mobile. > > To do this, we need two parts: > > 1. A way to point the TPS suite at a non-production Sync server (this is > https://bugzilla.mozilla.org/show_bug.cgi?id=1293426) > > and > > 2. An automated/CI way to run intensive TPS tests against Stage. (this > is being discussed in > https://bugzilla.mozilla.org/show_bug.cgi?id=1219456, but will probably > be broken out into a new bug soonish.)
Unless :jrgm objects, I think it would be useful to have a third part to this - a small set of TPS tests that continue to run against production, as a cheap and non-metrics-skewing validation that production is as it should be. Ryan _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
