Google Testing Blog: May 2015

GTAC 2015 Coming to Cambridge (Greater Boston) in November

Thursday, May 28, 2015

Posted by Anthony Vallone on behalf of the GTAC Committee

CambridgeToozdee and WenzdeeGTAC

31 comments

Multi-Repository Development

Friday, May 15, 2015

Author: Patrik Höglund roughly a hundred libraries

Figure 1. Holy dependencies, Batman!libphonenumber Updating Dependencies is Hard

Update the library to its latest release. If it’s been a long time since you did this, it can be quite risky and you may have to spend significant testing resources to ensure all the accumulated changes don’t break your application. You may have to catch up to interface changes in the library as well.

Cherry-pick the feature/bug fix you want into your copy of the library. This is even riskier because your cherry-picked patches may depend on other changes in the library in subtle ways. Also, you still are not up to date with the latest version.

Find some way to make do without the feature or bug fix.

How “Rolling” Works DEPS{ # ... 'src/third_party/webrtc': 'https://chromium.googlesource.com/' + 'external/webrtc/trunk/webrtc.git' + '@' + '5727038f572c517204e1642b8bc69b25381c4e9f', } 572703...DEPSrollinggetUserMedia has started crashing on Androidmany tests, on all platforms we ship on

Figure 2. Life of a Roll Patch. Bots That Can See the Future: “FYI Bots” DEPS

If all the FYI bots were green, we knew a roll most likely would go smoothly.

If the bots didn’t compile, we knew we would have to adapt Chrome to an interface change in the next roll patch.

If the bots were red, we knew we either had a bug in WebRTC or that Chrome would have to be adapted to some semantic change in WebRTC.

FYI “waterfall”main waterfall Making Gradual Interface Changes red blindness[1]API prime directive[2]class WebRtcAmplifier { ... int SetOutputVolume(float volume); }class WebRtcAmplifier { ... int SetOutputVolume(float volume, bool allow_eleven¹); }class WebRtcAmplifier { ... int SetOutputVolume(float volume); int SetOutputVolume2(float volume, bool allow_eleven); }

Roll into Chrome

Make Chrome use SetOutputVolume2

Update SetOutputVolume’s signature

Roll again and make Chrome use SetOutputVolume

Delete SetOutputVolume2

Resultsperformance tests Future Work: Optimistic Auto-rollingARB (AutoRollBot) References Footnotes

We actually did have a hilarious bug in WebRTC where it was possible to set the volume to 1.1, but only 0.0-1.0 was supposed to be allowed. No, really. Thus, our WebRTC implementation must be louder than the others since everybody knows 1.1 must be louder than 1.0.

6 comments

Testing Blog

GTAC 2015 Coming to Cambridge (Greater Boston) in November

Multi-Repository Development

Labels

Archive

Feed