On 06/14/2017 10:35 AM, Andrew Swan wrote:
On Wed, Jun 14, 2017 at 10:07 AM, Nathan Froyd <nfr...@mozilla.com <mailto:nfr...@mozilla.com>> wrote:On Wed, Jun 14, 2017 at 12:54 PM, Steve Fink <sf...@mozilla.com <mailto:sf...@mozilla.com>> wrote: > Whoa. Experiments aren't tested in automation? Whoa. We're going to still have to think about interface compat with external clients in a post-57 world? This is the first I've heard of this. > Can they be, please? At least snapshotted versions. +1 Almost anything automation-related would be better than "hope peers think hard about this".I'm not sure what you mean by "they". We have support in the browser for loading experiments, but we don't have a way to sign them for running in release. So some individuals have created experiments that they have used locally but there is no centralized list of them and none of them are widely used. Making experiments more usable by creating a process for getting experiments reviewed and signed is something we'd like to do and a testing strategy certainly needs to be part of that. But realistically that is not going to happen until 57 is out the door.
Ok, fair enough. I just sort of assumed that Experiments were a more actively used thing already, but didn't actually look at current usage. Hopefully it'll grow into something more, and we'll have a good story for ensuring that they don't continually break. Knowing the current state, I guess that addresses my concern. (Well, not the concern that we don't have a great story for deeper extensions yet, but at least I understand now why CI testing isn't really where we are yet.)
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
