1. Different Focus Areas
   1. Search Engine
   2. Apps
   3. Ads
   4. Mobile OS, etc.
2. No "Separate" Testing Organization
   1. Testing exists under "Engineering Productivity" area
   2. Engineering Productivity
      1. Product Team
         1. Develops tools to help with productivity
      2. Service Team
         1. Handles service, issues, etc.
      3. Embedded Engineers
         1. Loaned to teams on need basis
   3. Product teams own quality
      1. Testers enable developers to test
      2. SET (Software Engineer Testing) creates Test Framework
      3. Developer are responsible for testing
      4. Developers write Test Scripts
3. Quality != Test
   1. Without testing, it is impossible to build anything of quality.
   2. Development & Testing are mixed until they are indistinguishable.
   3. Build little, Test little
      1. Developer does most of the testing
   4. Get developers fully vested int the quality equation
   5. Bug Prevention >>> Bug Detection
   6. Testers might not be involved from the beginning but testing is!
4. Roles @ Google
   1. Software Engineer (SWE)
      1. Write Functional Code
      2. Works towards Bug Prevention
   2. Software Engineer in Test (SET)
      1. Write Test Framework
   3. Test Engineer (TE)
      1. Does User Focused Testing
      2. Involved in late stages of development
         1. Raise alarms
5. Quality is a work in progress
   1. A product must go through number of channels & prove it's worth
   2. Canary Channel
      1. Used for code suspected to be not fit for release
   3. Dev Channel
      1. Used for day-to-day work by devs
   4. Test Channel
      1. Internal Dog Food
   5. Beta / Release Channel
      1. Extreme Exposure
      2. Get Feedback & Iterate
   6. Initial development is not about quality, it is about proving the concept & feasibility
6. Test Scope Terminiology
   1. Small
      1. Automated Tests
      2. Unit Tests
      3. Written by SWEs
   2. Medium
      1. Automated or Manual
      2. Checks if the neighboring features interoperate.
   3. Large
      1. Covers 3 or more features
      2. Checks if the software does what the user expects?
   4. If a test doesn't need human cleverness or intuition, it should be automated.
7. Based on James Whittaker's blog posts on testing.googleblog.com