读书笔记 - How Google Test Software(3)

　　Google Feedback - 方便报缺陷的系统

　　Quality Bots Experiment - 对比系统

　　对比页面变化，在Chrome的浏览器的测试，每个版本浏览器都需要对比N个网页确认没有破坏掉什么功能。

　　http://code.google.com/p/qualitybots/

　　BITE

　　BITE stands for Browser Integrated Test Environment. The Browser Integrated Testing Environment, or BITE, is an open source Chrome extension (http://code.google.com/chrome/extensions/index.html)

　　Report a bug

　　Viewing bugs

　　Record / Playback

　　Executing Manual and Exploratory Tests with BITE

　　Google Test Analytics - Risk Analysis

　　Support ACC - Link test case / bugs

　　we're open sourcing Test Analytics (http://code.google.com/p/test-analytics/), a tool built at Google to make generating an ACC simple.

　　Record/Playback Framework

　　Record/Playback Framework (RPF) works in the Browser Integrated Test Environment (BITE) (http://googletesting.blogspot.com/2011/10/takebite-out-of-bugs-and-redundant.html).

　　SETs 和 TEs的区别

　　SETs' roles and TEs' roles are related but different in fundamental ways. I've been both and managed both. Look at the lists that follow and find which description most fits you—maybe you should switch roles.

　　You might be an SET if

　　You can take a specification, a clean whiteboard, and code up a solid and efficient solution.

　　When you code, you guiltily think of all the unit tests you should be writing. Then, you end up thinking of all the ways to generate the test code and validation instead of hand crafting each unit test.

　　You think an end user is someone making an API call.

　　You get cranky if you look at a poorly written API documentation, but sometimes forget why the API is interesting in the first place.

　　You find yourself geeking out with people about optimizations in code or about looking for race conditions.

　　You prefer to communicate with other human beings via IRC or comments in check-ins.

　　You prefer a command line to a GUI and rarely touch the mouse.

　　You dream of machines executing your code across thousands of machines, beating up algorithms, and testing algorithms—showing their correctness through sheer numbers of CPU cycles and network packets.

　　You have never noticed or customized your desktop background.

　　Seeing compiler warnings makes you anxious.

　　When asked to test a product, you open up the source code and start thinking about what needs to be mocked out.

　　Your idea of leadership is to build out a great low-level unit test framework that everyone leverages or is highly exercised millions of times a day by a test server.

　　When asked if the product is ready to ship, you might just say, "All tests are passing."

　　You might be a TE if

　　You can take existing code, look for errors, and immediately understand the likely failure modes of that software, but don't much care about coding it from scratch or making the change.

　　You prefer reading Slashdot or News.com to reading other people's code all day.

　　You read a spec for a product that is half-baked, you take it upon yourself to fill in all the gaps, and just merge this into the document.

　　You dream of working on a product that makes a huge impact on people's lives, and people recognize the product you work on.

　　You find yourself appalled by some websites' UI and wonder how they could ever have users.

　　You get excited about visualizing data.

　　You find yourself wanting to talk to humans in meat space.

　　You don't understand why you have to type "i" to start typing in a certain text editor.

　　Your idea of leadership is nurturing other engineers' ideas and

　　challenging their ideas with an order of magnitude more scale.

　　When asked if the product is ready to ship, you might say, "I think it's ready."

　　It is important for testers to figure out who they are. Often, TEs are simply seen as SETs who don't code as much or as well. The reality is that they see things that people with their head in the code all day will never see. SETs should also realize they aren't TEs and let go of any guilt or pressure to find UI issues or think about the system overall or competitive products; focus instead on high quality, testable, and reusable modules and amazing automation.

　　It takes a diverse family of testers to raise an amazing product.

原文转自：http://blog.csdn.net/o2o_o2o/article/details/8944072