Notes: How Google Tests Software

1. Reviewing design documents is purposeful and not like reading a newspaper. It is really important to create a test plan.
2. Good practice while testing through considering ACC(Attributes-> core value that makes our products different(ie. fast, secure); Component -> class that changes in source code(test all components); Capability -> The actions the system performs at the command of the user.) 
3. If you have trouble enumerating attributes in anything more than a few minutes, then you do not understand your product well enough to be an effective tester.
4. The most important aspect of capabilities is that they are testable.
5. Calculate risk analysis really crucial to define test priority  (frequency  of failure * estimated impact to the user)
6. Crowdsourcing is a solution for the fact that testers are few in number and have limited resources and that users are great in number and possess every variation of hardware and environment combinations.
7. TE more close to the user perspective
8. Manual exploratory testing and tours should prove valuable in finding end user-focused issues around simplicity, functionality, usability, and so on. 
9. SDETs main responsibility implement test code.
10. SDET interviewers focus on how the candidate thinks about the solution, not so much the elegance of the solution itself.
11. As SDET is really important to know component dependencies that change during the testing process in order to be able to implement good unit testing
12. SETs are developers who provide testing features. A framework that can isolate newly developed code by simulating an actual working environment (a process involving such things as stubs, mocks, and fakes)
13. Introduction to Google test tools (BITE, Selenium, Test Analytics, Google Test Management)
14. smoke tests for validating end-to-end integration scenarios and write as small a test as possible.