Embedded Files
1) [QA] 2014 Winter Olympics project (an example among 140+ QA tasks)
client: internal project of Google [Seoul, South Korea]
problem: Google needed to test newly developed Live Results and Knowledge Panels of Winter Olympics to make sure UI, click behavior, and data are working as intended on 1st-tier platforms
platform: IE 8, 9, 10 on Windows; Chrome, Firefox, Safari, Opera on Mac OS; Chrome, Safari, Google Search App on iOS 5, 6, 7 on iPad and iPhone; stock, Chrome, Google Search App on Android KitKat, Jelly Bean, Ice Cream Sandwich, Gingerbread on Android mobile and tablet devices (c.f. some browsers were not tested due to internal policy)
my role and contribution: communication with software engineers (70%), communication with global team (100%), device procurement/preparation (70%), creation of testing doc (90%), QA testing (55%)
my approach:
A. before QA
background research: read internal documents (e.g. PRD (product requirement document), mock-up, QA doc) and researched Winter Olympics to understand new feature background
previous case research: communicated with global offices to improve Olympics QA testing than previous years
scope clarification: discussed testing scope with PM/software engineers for query (including natural language), platform (device, OS, browser), use-case, click behavior (or flow), and TTS to measure length and depth of QA task
B. during QA
1st step: tested triggering, UI, click behavior, and data without internal URL parameters on desktop, then filed bugs on internal issue tracker
2nd step:
[for English] tested triggering, UI, click behavior, and data on mobile and tablet devices (rotation test included), then filed bugs on internal issue tracker
[for additional LTR (Russian, Korean), RTL (Arabic)] tested triggering, UI, data on desktop, mobile and tablet devices (rotation test included), then filed bugs on internal issue tracker
C. after QA
verification: tested fixed bugs on demo/live URL on relevant platform
my noticeable contribution: led QA testing for a global service by thoroughly manual-testing on major platforms by OS, form factor, browser in terms of UI, click behavior, data and flow; provided user-centric and trendy recommendations via heuristic approach to increase usability
impact: first time for Google to simultaneously launch new features in 40 languages on mobile, tablet, desktop and Google Now
2) [process improvement] self-initiated 20% project
client: internal project of Google Korea [Seoul, South Korea]
problem:
A. unstandardized QA request: engineers have constantly asked how to create QA requests; when requests were made, they often miss important documents such as mock-ups and product requirement documents
B. dispersed testing device: testing devices were spread in multiple cabinets
C. knowledge gap: due to no full-time-employee status and 1-year contract limitation, the influence level and the quality of QA results have been fluctuating because the nature of temps is that one person starts working and the previous person leaves
my role and contribution: idea generation and discussion (80%), website creation (100%), website promotion (100%)
my approach:
A. standardization of QA request: systematized existing QA process to match corporate standard, spearheading the new process to software engineers, tech leads, product managers and Korea QA
B. creation of communication website: creatively reduced communication cost between software engineers and Korea QAs by self-initiating to develop internal website containing status dashboards, analysis reports and QA education materials used by engineers, Korea QA and other departments of Google
C. restructuring testing rental device: restructured testing device rental process to be convenient for QAs and engineers by integrating online and offline rental system
my noticeable contribution: identified and solved repetitive and non-standardized system
impact: this practice was shared with various teams at Google; reduced communication and increased work efficiency and adaptability
Page updated
Google Sites
Report abuse