Reasons to Repeat Tests
http://www.satisfice.com/repeatable.shtml
by James Bach
- 10月 20 週一 200815:36
Reasons to Repeat Tests
Reasons to Repeat Tests
http://www.satisfice.com/repeatable.shtml
by James Bach
- 10月 14 週二 200810:51
QA，你都在掃廁所嗎？
QA，你都在掃廁所嗎？
這是一個朋友forward給我的文章, 這篇正好呼應上一篇的觀念(如何評量是否是一個好的QA). 若是你只是在找bug, 而不去想team目前遇到的問題是什麼. 就算你bug找的再多, 也不會有人特別感謝你.
所以, 不要再侷限QA只是在找bug, 不要只是在開發週期後段才開始動作. 否則, QA，你只是花力氣在掃廁所
- 10月 10 週五 200815:36
什麼是Test Architect
什麼是Test Architect
最近有人問我, test architect在做些什麼? 因為公司想要為走tech track 的人, 訂定一些方向. 可惜在國內這樣的資料一直很少, 畢竟testing在國內是十分冷門的工作, 更不用談還有test architect這樣的職位.
在網路上google了一下, 還是以微軟員工提到的最多, 但是其他也是不少. 可見在國外她們還是蠻需要這樣角色的人
- 10月 07 週二 200810:09
如果微軟你這麼擅長測試, 那你的軟體品質為何還這麼爛?
如果微軟你這麼擅長測試, 那你的軟體品質為何還這麼爛?
if Microsoft is so good at testing, why does your software suck?
http://blogs.msdn.com/james_whittaker/archive/2008/08/11/if-microsoft-is-so-good-at-testing-why-does-your-software-suck.aspx
- 10月 05 週日 200810:00
如何測試 Daily Build
如何測試 Daily Build
Testing A Daily Build
http://blogs.msdn.com/steverowe/archive/2007/10/25/testing-a-daily-build.aspx
- 9月 22 週一 200815:28
如何有效開立test case: feature-driven v.s purpose-driven
如何有效開立test case: feature-driven v.s purpose-driven
通常我們開立test cases時, 都是以feature為導向, 來分配工作. 例如QA 甲測試 feature 1, QA 乙測試 feature 2. 然後可能給1~2週讓他們開立test cases, 之後再進行test case review. 可是這樣做我們遇到了一些問題
1. 大家都只會開functional的test cases
2. 太慢才能給feedback, 因為要等test case全部開完才能給feedback
3. TC 太多, 大家沒有空仔細去看完. 因為1~2週開完的test case量實在不少
- 8月 26 週二 200811:05
Bug bash
Bug bash
我一直以為自己對testing 很了解, 但是昨天聽到一個term是我所不知道的.所以世界真的很大, 要一直告訴自己天外有天, 人外有人, 還是要持續學習.
在這裡跟大家分享一下, 什麼是bug bash
在wiki中的解釋是這樣的
Bug bash is where all the developers, testers, program managers, usability researchers, designers, documentation folks, and even sometimes marketing people, put aside their regular day-to-day duties and pound on the product to get as many eyes on the product as possible.
http://en.wikipedia.org/wiki/Bug_bash
就是每個人放下手邊的工作,這段時間進行測試, 找出具有潛在性的bug, 例如UI 那裡不好用,需要重新設計! 或是哪些error handling不盡理想. 找到越多越好,寧可錯殺, 也不要放掉一個! 每個人需要浴血奮戰, 絞盡腦汁在有限的時間找出bug.
要鼓勵各部門, 不同角色, 或是不同領域交叉搜索,因為新的思路和角度通常有助於發現更多的Bug
儘管這是一個測試活動，但參與者並不僅限於測試人員。專案經理，開發人員甚至於高層管理人員都應參加，如同全民動員。目的是要集思廣益
不一定針對全部的功能, 可以針對某一部份,某個主題(某各特別的或是重要的功能, 效能, 安全性、使用者界面可用性、國際化和本地化等) 或是某個人做的功能去做測試.
如果必要的時候, 需要加一些獎勵, 來鼓勵來找到最多bug或是最有價值bug的人.中間還可以供應點心, 讓大家能全新全意致力於找bugs
時間上2天, 1 天, 一個下午, 2hr, 或是中午吃飯時間都可以.
- 7月 02 週三 200814: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.
