- Jul 24 Thu 2008 22:24
-
"早上3小時完成一天工作" - 摘要 (2)
- Jul 24 Thu 2008 22:15
-
"早上3小時完成一天工作" - 摘要 (1)
- Jul 16 Wed 2008 21:22
-
Learning C# : string example (1)
- Jul 15 Tue 2008 18:22
-
什麼是QA 經理要做的事
最近公司在討論QA manager到底要做些什麼？有哪些挑戰是我們目前大家所共同遭遇的？一開始大家討論就很熱烈，但是很快地，答案就收斂下來，因為大家的心中的痛都一樣。
首先，在工作項目方面我們認為QA manager有以下項目：
1. 人員的管理：包含指導(coach)、發展(develop)、生涯規劃(career planning)等等。
- Jul 02 Wed 2008 14:53
-
Is Unit Testing a kind of White box testing?
Most people think unit testing is a kind of white box testing. So when they write test program for the unit under test, they say "We have done white box testing" It's a big big BIG mistake!!!
Let's see the definition of these terminologies first
1. White box testing: is a test case design moethod that uses the control structure of the procedural design to derive test cases
2. Black box testing: focuses on the functional requirements of the software.
That is black box testing enable the RD to derive sets of input conditions that will fully exercise all functional requirements for a program
That is black box testing enable the RD to derive sets of input conditions that will fully exercise all functional requirements for a program
3. Unit testing: focuses verification effort on the smallest unit of software design - the module, class, or function.
From the definition, if you want to use white box testing to test your program, you must consider the control structure of the program under test. For example: branch, condition, loop, path, and so on. It means you have to analyze the path structure first. That's why you have heard about statement coverage, branch coverage or condition coverage because they want to use these criteria to measure your testing effort of white box testing. Therfore, when you do unit testing, you can use white box testing or black box testing. Depend on how many resources you have. Due to the size of unit is small, it's a good chance to use white box testing. If the number of unit is too large, people might use black box testing to save time.
In Taiwan's software industry, most engineers just input some values to their program and check whether they are correct or not. Therefore it's just a kind of example appling black box testing to do unit testing.
- Jun 25 Wed 2008 23:01
-
測試自動化經驗談 (2)
- Jun 22 Sun 2008 22:49
-
測試自動化經驗談 (1)
測試自動化做了幾年後，累積了一些心得，希望能夠跟大家交流一下。
1. 僱用開發能力強的QA
一般公司的QA通常沒有coding能力或是coding經驗不夠，因此若是要測試自動化有顯著效果，必需能僱用開發能力強的QA來應付以下狀況：
(1) 需求經常變動
每個人都知道需求是一直在變動的，因此RD常常需要修改程式來配合。此時若是QA的開發能力不強，他是無法在短時間反應這樣的變動。再加上若是手動測試(manual testing)的工作忙碌，不難想像測試自動化會放到一旁，最後甚至可能就會無疾而終。
(2) 測試結果的確認很複雜
有時候寫測試程式不一定很難，但是要檢查測試結果是否正確，卻不是一件簡單的事。例如要檢查安裝程式是否安裝正確，你可能要檢查files、 registry keys、services、processes等等是否正確
