Google Testing Blog

From QA to Engineering Productivity

Tuesday, March 22, 2016

By Ari Shamash

Test Engineers (TEs) -- tested new products and systems integration

Release Engineers (REs) -- pushed bits into production

Site Reliability Engineers (SREs) -- managed systems and data centers 24x7.

longer and longerfix themautomation

Test Engineers (TEs) -- With their deep product knowledge and test/quality domain expertise, TEs focused on what should be tested.

Software Engineers in Test (SETs) -- Originally software engineers with deep infrastructure and tooling expertise, SETs built the frameworks and packages required to implement automation.

Automated tests became more efficient and deterministic (e.g. by improving runtimes, eliminating sources of flakiness, etc.)

Metrics driven engineering proliferated (e.g. improving code and feature coverage led to higher quality products).

there was much rejoicingwebdriverimprovementsprotractorespressoEarlGreymartian proxykarmaGoogleTestconferencessoftware engineerspublished articlesTest-Driven Developmentother phases in the development cycle became the bottleneck

Extending IDEs to make writing and reviewing code easier, shortening the “write code” cycle

Automating release verification, shortening the “release code” cycle.

Automating real time production system log verification and anomaly detection, helping automate production monitoring.

Automating measurement of developer productivity, helping understand what’s working and what isn’t.

We empowered the SETs to choose a new titleSETITE

33 comments

EarlGrey - iOS Functional UI Testing Framework

Tuesday, February 16, 2016

By Siddartha Janga on behalf of Google iOS Developers YouTubeGoogle CalendarGoogle PhotosGoogle TranslateGoogle Play Music

Powerful built-in synchronization : Tests will automatically wait for events such as animations, network requests, etc. before interacting with the UI. This will result in tests that are easier to write (no sleeps or waits) and simple to maintain (straight up procedural description of test steps).

Visibility checking : All interactions occur on elements that users can see. For example, attempting to tap a button that is behind an image will lead to test failure immediately.

Flexible design : The components that determine element selection, interaction, assertion and synchronization have been designed to be extensible.

Apache licensegetting started guideCocoaPods

9 comments

GTAC 2015 Wrap Up

Tuesday, December 08, 2015

by Michael Klepikov and Lesley Katzen on behalf of the GTAC CommitteeGTACGoogle Cambridge

Video RecordingsPresentations

Our 82 survey respondents were mostly (81%) test focused professionals with a wide range of 1 to 40 years of experience.

Another 76% of respondents rated the conference as a whole as above average, with marked satisfaction for the venue, the food (those Diwali treats!), and the breadth and coverage of the talks themselves.