软件测试的概念及其分类

1、Test concept 软件测试的概念软件测试的概念l是使用人工或者自动手段来运行或测试某个系统的过程，其目的在于检验它是否满足规定的需求或弄清预期结果与实际结果之间的差别。 测试目标l1发现一些可以通过测试避免的开发风险。l2实施测试来降低所发现的风险。l3确定测试何时可以结束。l4在开发项目的过程中将测试看作是一个标准项目。软件测试分类软件测试分类l是否关注软件结构与算法 黑盒黑盒和白盒测试l是否执行被测试软件 静态测试和动态测试l基于测试的不同阶段 单元测试，集成测试集成测试，系统测试，验收测试系统测试，验收测试从软件开发的过程按阶段划分有lA.单元测试lB.集成测试集成测试lC.确认

2、测试 lD.系统测试 (system test)lE.验收测试 (Acceptance test)lF.回归测试回归测试 (Regression test)lG.Alpha测试lH.Beta测试自动化测试的概念及其常用的测试方法自动化测试的概念及其常用的测试方法l什么是自动化测试l冒烟测试l回归测试自动化测试自动化测试l自动化测试1是把以人为驱动的测试行为转化为机器执行的一种过程。通常，在设计了测试用例并通过评审之后，由测试人员根据测试用例中描述的规程一步步执行测试，得到实际结果与期望结果的比较。在此过程中，为了节省人力、时间或硬件资源，提高测试效率，便引入了自动化测试的概念。通常适合于通常适

3、合于软件测试软件测试自动化的场合自动化的场合l(1)回归测试，重复单一的数据录入或是击键等测试操作造成了不必要的时间浪费和人力浪费；l(2)此外测试人员对程序的理解和对设计文档的验证通常也要借助于测试自动化工具；l(3)采用自动化测试工具有利于测试报告文档的生成和版本的连贯性；l(4)自动化工具能够确定测试用例的覆盖路径，确定测试用例集对程序逻辑流程和控制流程的覆盖。冒烟测试冒烟测试l关于冒烟测试，应该是微软首先提出来的一个概念，和微软一直提倡的每日build有很密切的联系。具体说，冒烟测试就是在每日build建立后，对系统的对系统的 基本功能进行简单的测试基本功能进行简单的测试。从这一点看和

4、所谓的（Acceptance Test）”非常相似。不同之处就在于他们执行的频率和被测的版本不同。 冒烟测试的目的冒烟测试的目的l 简单的说，就是先保证系统能跑的起来，不至于让测试工作做到一半突然出现错误导致业务中断。目的就是先通过最基本的测试，如果最基本的测试都有问题，就直接打回开发部了，减少测试部门时间的浪费 回归测试回归测试l回归测试指在软件维护阶段，为了检测代码修改而引入的错误所进行的测试活动。回归测试是软件维护阶段的重要工作，有研究表明，回归测试带来的耗费占软件生命周期的1/3总费用以上。 Expedia EWE Integration testlTrunk daily test (

5、smoke, acceptance)lRegression test lSerialization testlPre production testlDR test (Automation&Manual)lMonthly pop up test (Manual)-Browser testImportant Release Terms and DefinitionslFeature Set:A branch in Source Depot (perforce) where developers develop new code. This can consist of any numbe

6、r of projects, on one feature set branch. It is up to individual teams to decide how many teams / projects should be involved in any feature set. A feature set is deployed and tested on a common hardware environment called the Pre Merge Platform (PMP). Feature set naming convention: FSXXXXX. lFeatur

7、e Set Branch: The first step towards getting a project released, it is the source depot branch that developers start coding into. To begin coding a project in a Feature Set Branch, that project needs to be spec ready. Daily Test Environment ValidationlThe following test suites are run on a daily bas

8、is to ensure that the test environments are stable. Smoke Tests are run to identify any problems to the test environments prior to the start of the work day in Bellevue. When problems are found they are reported and actions taken to get them fixed to keep EWE test & development work moving forwa

9、rd. Run on Trunk every day if have time.Smoke TestinglThe EWE (Expedia Worldwide Engineering) smoke test is designed to run prior to builds being handed off to test teams for further testing and is intended to reveal simple failures severe enough to reject the build. lThe tests consist of a subset o

10、f test cases that cover the most important functionality of the site (up to, but not including booking).Acceptance TestinglAcceptance testing is the process of testing a Trunk build against specific test cases to determine the suitability of the build for further in-depth testing. Early in the relea

11、se cycle, Acceptance testing could be limited to major functional areas depending on the available time frame. As we progress towards RTS, testing will become more detailed and they should cover all areas of the product, including regression cases.Regression TestinglThe intent of regression testing

12、is to provide a general assurance that no additional errors were introduced in the process of fixing other problems or adding new features. This automation is generally run once per release with the intent of uncovering any existing software errors by testing existing functionality. lTwo release one

13、 month, like 08-r1, 08-r3 on August.lRun on Integration, Soak. Pre Production testlPPE is as close to an exact replica of production as we have. These tests are run on PPE to validate that everything was propped correctly in our pre-release RTW test run. If all tests pass here, next step is RTW.Brow

14、ser Testing:lAs the name suggests, this testing is done to verify the new features works with most of the browsers. The Test team uses a 3-tiered approach when doing browser configuration testing; Browsers in the first tier are those with current or anticipated high usage. These browsers are subject

15、 to a full test pass (Test use these browsers in their day-to-day testing for all product Team.). With the second tier browsers, Test will run a light test pass; And in the third tier, Test will simply verify that we can make a search and booking; booking on the major shopping paths. MilestonelZD: Acronym for Zero Defects. Every release and every feature set has a Zero Defects Milestone. Before a feature set can be included in a release, it must reach Zero Defects by the Zero Defects