《How Google Tests Software》的笔记-第29页
- 章节名：Automation Planning
- 页码：第29页 2013-04-07 15:04:10
The larger an automation effort is, the harder it is to maintain and the more brittle it becomes as the system evolves. It's the smaller, more special purpose automation that creates useful infrastructure and that attracts the most SWEs to write tests.At Google, SETs take the following approach.We first isolate the interfaces that we think are prone to errors and create mocks and fakes so that we can control the interactions at those interfaces and ensure good test coverage.The next step is to build a lightweight automation framework that allows the mocked system to be built and executed. That way, any SWE who writes code that uses one of the mocked interfaces can do a private build and run the test automation before they check their code changes into the main codebase, ensuring only well tested code gets into the codebase in the first place.This is one key area where automation excels: keeping bad code out of the ecosystem and ensuring the main codebase stays clean.
Jessie对本书的所有笔记 · · · · · ·
Test is just another feature of the application, and SETs are the owner of the testing fea...
Indeed, SETs have the one major advantage of being the engineer on the team with the broad...
The Test Engineer (TE) plays a related but different role where the focus is on user impac...
The first advice toward this end is know your product. Given any question about how to use...
说明 · · · · · ·