Systems Thoughts

今天在Google Testing Blog看到一篇好文,不过看看Google的Tester入职门槛:
C/C++/Java/Python – Strong
PHP/Perl/Vbscript(??) – Good
Script language (awk和sed) – Strong
其实跟Developer差不多了…不过一般developer可能应聘不上Tester因为他们对开发流程中的测试了解有限。

什么？你说blogspot在国内看不了？我还以为现在机器翻墙都标配了…. 那我跟着转一下都有几种framework吧。

The Input Domain Framework treats software as an input-output mechanism. Subscribers of this framework think in terms of sets of inputs, rules about which inputs are more important and relationships between inputs, input sequences and outputs. This is a common model in random testing, model-based testing and the testing of protocols and APIs. An applicant who uses this framework will talk about which inputs they would use to test a specific application and try to justify why those inputs are important.

The Divide and Conquer Framework treats software as a set of features. Subscribers begin by decomposing an app into its features, prioritizing them and then working through that list in order. Often the decomposition is multi-layered creating a bunch of small testing problems out of one very large one. You don’t test the feature so much as you test its constituent parts. An applicant who uses this framework is less concerned with actual test cases and more concerned with reducing the size of the problem to something manageable.

The Fishbowl Framework is a big picture approach to testing in which we manipulate the application while watching and comparing the results. Put the app in a fishbowl, swirl it around in the water and watch what happens. The emphasis is more on the watching and analyzing than it is on exactly how we manipulate the features. An applicant who uses this framework chooses tests that cause visible output and large state changes.

The Storybook Framework consists of developing specific scenarios and making sure the software does what is is supposed to do when presented with those scenarios. Stories start with the expected path and work outward. They don’t always get beyond the expected. This framework tests coherence of behavior more than subtle errors. Applicants who employ this framework often take a user’s point of view and talk about using the application to get real work done.

The Pessimists Framework starts with edge cases. Subscribers test erroneous input, bad data, misconfigured environments and so on. This is a common strategy on mature products where the main paths are well trodden. Applicants who use this framework like to assume that the main paths will get tested naturally as part of normal dev use and dog-fooding and that the testing challenge is concentrated on lower probability scenarios. They are quick to take credit for prior testing, assume its rationality and pound on problematic scenarios.

如此看来我比较偏向Pessimists Framework，哈哈，不过我可是绝对的optimist