微軟的軟件測試流程

　　最近學習了淘寶網的測試流程，感觸很深，個人覺得流程特別適合淘寶網這個產品。由于之前曾Onsite微軟，對微軟的一些測試流程也有一定的了解，曾寫過關于微軟測試的一些總結，特將其share給各位師兄師姐，由于之前是用英文寫的，請大家湊合著看吧:

　　Involving testing field, all of us heard or touched lots of testing terms at Microsoft project more or less, such as : Black Box Test, White Box Test, Unit Test, Structural Test, Load Test, Ad hoc Test, Usability Test…. and so on. But few people can differentiate these and classify these and apply these at a complete degree. I just summarized these terms from a good reference, and hope to share these to you. Now here we go:

　　1. Classify these by test design method:

　　a. Black Box (During the test design, viewing the system as a “black box” and don’t know anything about the internal structure or process flow), also called Behavioral Test Design

　　b. Write Box (During the test design, the designer can “see” the internal structure and using these info to guide test case and test data)

　　c. Gray Box (Combined Black Box and Write Box test, in general using Black Box method to design test at first, then using Write Box method to perfect)

　　2. Classify these by test purpose:

　　a. Functional Test (Includes Unit Test, Integration Test, Scenario Test, System Test, Alpha/Beta Test)

　　b. Non-functional Test (Includes Stress/Load Test, Performance Test, Accessibility Test, Localization/Globalization Test, Compatibility Test, Configuration Test, Usability Test, Security Test)

　　3. Classify these by test phase and role

　　a. Smoke Test (The base verification test, cannot process the next step if the test is failed; sometimes choose the crucial test case to test the system)

　　b. Build Verification Test (One method of Smoke Test, run the case suite which can verify the system base function after the build is done, two outcomes after BVT: Self-test (pass); Self-hosed(fail))

　　c. Acceptance Test (The first test activity after the test team received the Self-test build, this is judged from test team; differentiate it with User Acceptance Test which is a test activity after system test and often done by customer or partner)

　　d. Regression Test (To ensure that the build has not regressed in anyway as a result of changes to the build and/or environment, often running passed tests again to ensure that they still pass)

　　e. Ad hoc Test (Also called Exploratory Test, a specific and undefined and short-lived activity, often used if the tester wants to try more scenarios with intuition, when the tester is testing the module according to test plan)

　　f. Bug Bash (Also called Bug hunt, all guys includes developers, tester, PM, other product members aim to find bugs using individual creativity and new test method, often only 1-3 days after each milestone)

　　g. Buddy Test (Each developer find a tester as buddy and build a Private Build and tester test the build and report bug to dev directly, often done after Unit Test and BVT)

　　4. Assign test activities through whole development cycle

　　上面說的主要是微軟的整個新的版本的一些流程，主要是V模型，但微軟也有很多的項目是采用XP。自己也接觸了很多微軟的Tester，感觸最大的是微軟的Tester的code能力，debug的能力，code review的能力都很強;而且我曾經問過微軟總部的一個Tester什么是微軟測試的最大創新，他說就是：測試就是開發，把測試和開發的界限打破，使測試和開發非常接近，而且雙方幾乎可以互換角色。由于小弟剛來沒有在淘寶參加過實際的項目經驗，對淘寶的測試流程了解不夠全面和客觀，望師兄師姐多多指導。

　　以后小弟會share更多的關于微軟的測試的一些細節(包括流程和手段)，那樣大家可能會理解的更加清楚和明白。計劃下次share微軟的bug管理流程。目前個人感覺與淘寶的有些差別。若知后事如何，請頂貼。!!

原文轉自：http://www.kjueaiud.com