2011年5月24日
#
摘要: 一個完整的自動化測試框架體系包含以下幾個部分：1、自動化測試框架；2、測試腳本以及測試數據管理；3、測試腳本的執行管理系統；4、測試結果的顯示與分析系統。其中最重要的是自動化測試框架部分。
閱讀全文
摘要: JUnit
JUnit是由 Erich Gamma 和 Kent Beck 編寫的一個回歸測試框架（regression testing framework）。Junit測試是程序員測試，即所謂白盒測試，因為程序員知道被測試的軟件如何（How）完成功能和完成什么樣（What）的功能。Junit是一套框架，繼承TestCase類，就可以用Junit進行自動測試了。
更多JUnit信息
閱讀全文
摘要: Have you wondered why certain programs are located under /bin, or /sbin, or /usr/bin, or /usr/sbin?
For example, less command is located under /usr/bin directory. Why not /bin, or /sbin, or /usr/sbin? What is the different between all these directories?
In this article, let us review the Linux filesystem structures and understand the meaning of individual high-level directories
閱讀全文
摘要: 當今互聯網的發展，已不是大魚吃小魚的時代，而是快魚吃慢魚的時代。互聯網產品的制勝原則就是一個字——“快”。在各種形態的產品研發中，我們始終貫徹如一的價值觀之一就是“快”，我們應該如何來理解和詮釋“快”？又會從哪些方面來執行貫徹這個原則呢？
閱讀全文
摘要: 軟件測試的十二個誤區大體總結如下：
1) 測試人員不需要了解軟件開發的知識：
這個很要命的，我們談到軟件測試人員未來的發展方向大致有：自動化測試，性能測試，測試管理，項目經理。這其中自動化測試和性能測試包括項目管理，都會要求對軟件開發有深入的理解，如何能設計一個好的自動化框架，好的性能測試用例，如何管理一個開發團隊，這都需要我們在軟件開發方面有所掌握。不單要掌握，而且要精通。此其一。
其二：如果不了解開發知識，測試人員很容易被開發人員牽著鼻子走，因為開發人員隨便一忽悠，你如果不了解個中奧妙，你一個字也說不上來。(以前我們討論 Cookie和Session，由于GoAhead不支持Session，只能用Cookie來控制，差點別開發人員忽悠了)
閱讀全文
摘要: 寫在前面：寫Android程序有一個很重要的原則，不阻塞UI線程。因此Android提供了5種方法來，讓一些耗時的作業在其它線程中執行，然后把結果返回給UI線程，以免阻塞UI線程。
閱讀全文
探討了軟件測試的可測試性，主要包括Controllability, Observability, Availability,Simplicity, Stability 和 Information.
HeuristicsOfSoftwareTestability.pdf
摘要: android的selector的用法：
首先android的selector是在drawable/xxx.xml中配置的。
先看一下listview中的狀態：
把下面的XML文件保存成你自己命名的.xml文件（比如list_item_bg.xml），在系統使用時根據ListView中的列表項的狀態來使用相應的背景圖片。drawable/list_item_bg.xml
閱讀全文
摘要: The Monkey is a command-line tool that that you can run on any emulator instance or on a device. It sends a pseudo-random stream of user events into the system, which acts as a stress test on the application software you are developing.
The Monkey includes a number of options, but they break down into four primary categories:
Basic configuration options, such as setting the number of events to attempt.
Operational constraints, such as restricting the test to a single packag
閱讀全文
摘要: Programmers can configure logging either by creating loggers, handlers, and formatters explicitly in a main module with the configuration methods listed above (using Python code), or by creating a logging config file. The following code is an example of configuring a very simple logger, a console handler, and a simple formatter in a Python module:
閱讀全文
摘要: Android系統中Looper負責管理線程的消息隊列和消息循環，具體實現請參考Looper的源碼。 可以通過Loop.myLooper()得到當前線程的Looper對象，通過Loop.getMainLooper()可以獲得當前進程的主線程的Looper對象。
閱讀全文
摘要: The list below defines some of the basic terminology of the Android platform.
.apk file
Android application package file. Each Android application is compiled and packaged in a single file that includes all of the application's code (.dex files), resources, assets, and manifest file. The application package file can have any name but must use the .apk extension. For example: myExampleAppname.apk. For convenience, an application package file is often referred to as an ".apk".
Re
閱讀全文
摘要: C.__init__(self[, arg1, ...] )
Constructor (with any optional arguments)
C.__new__(self[, arg1, ...] )[a]
Constructor (with any optional argu ments); usually used for setting up subclassing of immutable data types
C.__del__(self)
Destructor
C.__str__(self)
Printable string representation; str() built-in and print statement
C.__repr__(self)
Evaluatable string representation; repr() built-in and '' operator
閱讀全文
摘要: 本來這是個老生常談的問題，上周自成又分享了一些性能優化的建議，我這里再做一個全面的Tips整理，謹作為查閱型的文檔，不妥之處，還請指正；
如果你已經對yahoo這些優化建議爛熟于心，果斷點這里
閱讀全文
Five test auomation framework are discussed in this paper.
1) The Test Script Modularity Framework
2) The Test Library Architecture Framework
3) The Keyword-Driven or Table-Driven Testing Framework
4) The Data-Driven Testing Framework
5) The Hybrid Test Automation
摘要: 一、ASE(Android Scripting Environment)為Android系統帶來了腳本語言的技術，通過它我們可以編輯和執行腳本，和腳本解釋交互。腳本可以訪問多數Android API,目前有一個開源項目叫做Scripting Layer for Android (SL4A) ，提供了對python,javaScript, Lua等腳本的支持。ASE主要通過兩種方式來訪問 Android API,一種是通過JSON-RPC來訪問,另外一種通過BeanShell（Java語言的動態版本）直接訪問Android API。SL4AL架構如下圖：
閱讀全文
摘要: 2.你需要學習JAVA語言的基礎知識以及它的核心類庫 (collections，serialization，streams，networking， multithreading，reflection，event，handling，NIO，localization，以及其他)。
閱讀全文
1)
http://www.pythonchallenge.com/ 提供了不同level的Python題目，非常有趣的題目。做完一題后，把URL中的pc改為pcc可以看到上一題的答案
2)
http://projecteuler.net/ 里面有200多道題目，不要要求提交代碼，只要最終答案，提供用各種語言來解決問題。這里（
http://dcy.is-programmer.com/posts/8750.html）有部分題目的答案
非常好玩，有興趣的朋友，快來試試吧
看看 project euler 的第一道題：
If we list all the natural numbers below 10 that are multiples of 3 or 5, we get 3, 5, 6 and 9. The sum of these multiples is 23. Find the sum of all the multiples of 3 or 5 below 1000.
用 python 語言寫出來是：
print sum(i for i in xrange(1, 1000) if i % 3 == 0 or i % 5 == 0)
This is the first edition of what is expected to become a recurring series on InfoQ. The idea behind this minibook is that a number of InfoQ articles and interviews which deal with a particular topic (in this case, REpresentational State Transfer, or REST) are combined together to provide a detailed exploration suitable for both beginners and advanced practitioners.
Read More: http://www.infoq.com/minibooks/emag-03-2010-rest;jsessionid=1E2375E822D980824403DAD46588FAFE
摘要: #Trie Tree的基本特點
1）根節點不包含字符，除根節點外每個節點只包含一個字符
2）從根節點到某一個節點，路徑上經過的字符連接起來，為該節點對應的字符串
3）每個節點的所有子節點包含的字符串不相同
閱讀全文
摘要: The Bloom filter, conceived by Burton Howard Bloom in 1970, is a space-efficient probabilistic data structure that is used to test whether an element is a member of a set.False positivesare possible, but false negatives are not. Elements can be added to the set, but not removed (though this can be addressed with a counting filter). The more elements that are added to the set, the larger the probability of false positives
閱讀全文
摘要: These posts have garnered a number of interesting comments. I want to address two of the negative ones in this post. Both are of the same general opinion that I am abandoning testers and that Google is not a nice place to ply this trade. I am puzzled by these comments because nothing could be further from the truth. One such negative comment I can take as a one-off but two smart people (hey they are reading this blog, right?) having this impression requires a rebuttal. Here are the comments:
閱讀全文
摘要: One of the key ways Google achieves good results with fewer testers than many companies is that we rarely attempt to ship a large set of features at once. In fact, the exact opposite is often the goal: build the core of a product and release it the moment it is useful to as large a crowd as feasible, then get their feedback and iterate. This is what we did with Gmail, a product that kept its beta tag for four years. That tag was our warning to users that it was still being perfected. We removed
閱讀全文
摘要: Lots of questions in the comments to the last two posts. I am not ignoring them. Hopefully many of them will be answered here and in following posts. I am just getting started on this topic.
閱讀全文
摘要: Android applications are, at least on the T-Mobile G1, limited to 16 MB of heap. It's both a lot of memory for a phone and yet very little for what some developers want to achieve. Even if you do not plan on using all of this memory, you should use as little as possible to let other applications run without getting them killed. The more applications Android can keep in memory, the faster it will be for the user to switch between his apps. As part of my job, I ran into memory leaks issues in Andr
閱讀全文
摘要: The Java community is now swamped with discussions about Oracle's patent suit against Google's Android platform. I've been contributing my opinion in several places, but there is one critical topic that needs repeating the same comments everywhere... so, this blog spills the beans once and completely.
閱讀全文
摘要: Activities in the system are managed as an activity stack. When a new activity is started, it is placed on the top of the stack and becomes the running activity -- the previous activity always remains below it in the stack, and will not come to the foreground again until the new activity exits.
閱讀全文
摘要: The one question I get more than any other is "How does Google test?" It's been explained in bits and pieces on this blog but the explanation is due an update
閱讀全文
摘要: Dependency injection asks us to separate the new operators from the application logic. This separation forces your code to have factories which are responsible for wiring your application together. However, better than writing factories, we want to use automatic dependency injection such as GUICE to do the wiring for us. But can DI really save us from all of the new operators?
閱讀全文
摘要: Everyone seems to think that they are writing OO after all they are using OO languages such as Java, Python or Ruby. But if you exam the code it is often procedural in nature
閱讀全文
By James Whittaker
I’ve had a number of questions about the SET role and it seems I have confused folks when I say that the SWE is a tester and the SET is a tester and at the same time the SWE is a developer and the SET is a developer. What could possibly be confusing about that?
Oh, yeah. Right.
My next series of posts are going to detail the role of the SET and all will eventually be clear but some clarification on career path seems worthwhile.
SETs are developers who write test code and automation as their primary task. They are in every sense of the word a developer. When we interview SETs, SWEs are on the interview loop and SWE questions are asked. They are not all of the interview, but they are part of it.
This means that the skill set that our SETs possess makes them perfect candidates for switching to the SWE role. There is neither incentive nor deterrent to do so. SETs and SWEs are on the same pay scale and bonus structure (I have both roles reporting to me so I have real visibility into salary data) and their promotion velocity (again based on actual data) is roughly equivalent. This means that SETs have no outside influences to prompt them one way or the other.
The key factor is really the type of work you are doing. SETs who find themselves involved in SWE work usually convert to SWE. SWEs are also drawn in the opposite direction. Much of this happens through our 20% time work. Any SET interested in SWE work can take on a 20% task doing feature development. Any SWE interested in automation can find a group and sign up for a 20%. Right now I have both SWEs and SETs involved in such cross pollination.
The ideal situation is that the title reflects the actual work that you are involved in. So if an SET starts doing more feature dev work than automation, he or she should convert, same for SWEs doing automation work. In my time here, conversions in both directions have happened, but it is not all that common. The work of both roles is engaging, interesting and intense. Few Googlers are walking around bored.
Bottom line: do the work you are passionate about and capable of and the right job title will find you.
一、概念
靜態分派（Static Dispatch），發生在編譯時期，分派是根據靜態類型信息發生的，方法重載就是靜態分派。
動態分派（Dynamic Dispatch），發生在運行時期，動態分派動態地置換掉某個方法。面向對象的語言用動態分派實現多態性。
Java語言支持靜態多分派和動態的單分派，利用設計模式Java可以實現Double Dispatch，即訪問者模式。
二、Visitor Pattern
目的：封裝一些施加于某種數據結構元素之上的操作。
UML圖：
主要原理：“反傳球”，Element來Visitor之間二輪調用，調用過程中用sinlge dispatch確定類型