测试策略3999790493
发布时间:2020-09-24 来源: 精准扶贫 点击： 
The development of a test strategy is a multi-step process of analysis : 1. Analyze requirements.
2. Assess risk.
3. Define scope of testing.
4. Determine test approach.
5. Determine entry and exit criteria. 一个测试战略的设计是一个多步调的阐发历程：
1. 阐发需求。
2. 评估风险。
3. 界说测试范畴。
4. 确定测试要领。
5. 确定进入和退出条件。
Once the requirements and risks of a project are well-understood, the next step in test planning is to determine the test strategy. The test strategy answers the following questions: Why are we testing? What do we plan to do? What do we plan not to do?
只要项目的需求和风险被准确理解，测试筹划的下一步就是确定测试战略。测试战略解决下列问题：为什么我们要测试？我们要做些什么？我们筹划不做些什么？
Your test strategy must include a clear definition of the scope of your testing. Your scope may be determined in part by your team"s responsibility. A large development project may have multiple test teams working on it, each of which is responsible for a different aspect of the project. Even a small project has different levels of test, as described in the module Test Levels and Activities. Your scope includes the levels of test that you cover.
你的测试战略必须包罗你对测试范畴的一个明确界说。你的范畴可能部分取决于你团队的责任。在大型生长项目里，可能有多个测试团队同时事情，每一个
小组卖力项目的差别方面。像在测试阶段和运动中描述的一样，纵然是很小的项目，也有差别水平的测试。你的范畴包罗你卖力的范畴内的测试阶段。
The scope of your testing is also affected by the scope and nature of the project itself. For example, the scope of testing may be smaller for a small service release to an existing product than for a new product.
你的测试范畴也会因为项目自己的范畴和性质而受到影响。例如，对付一个新产物来说，一个准许生产的产物中的一个小办事的测试范畴更小。
To determine the test approach, ask questions like these for each of the project features and attributes: ? What testing is planned for this feature or attribute?
? What customer problem does this feature solve?
? What announcement claims will we be making about this feature?
? What automation will we used to develop the tests for this feature?
要确定测试要领，为检测项目的成果和属性，必须提出下列问题，：
1、为测试成果或属性，要进行怎么样的测试？ 2 此成果解决客户的哪些问题？
3 针对这个特点，我们要做出怎样的陈诉？
4 我们将用什么自动化东西或技能来进行这项成果的测试？ To determine when to start and end testing, identify entry and exit criteria by answering the following questions:
为了决定何时开始和结束测试，凭据下列问题的答案，确定进入和退出条件：
? During the development process, can the tests we"ve defined be executed in an effective and
efficient manner?
? As the product continues to progress, when are we are finished?
1 在开发历程中，我们界说的测试能否以有效和高效的方法执行？
2 随着产物的不绝生长，我们什么时候能够完成？ In order for entry and exit criteria to be effective, they must have three common attributes. ? Entry and exit criteria must be meaningful.
? Entry and exit criteria must be measurable.
? Entry and exit criteria must be achievable.
为了进入和退出条件能够生效，就必须有 3 个配合属性。
进入和退出标准，必须是有意义的。
进入和退出标准，必须是可权衡的。
进入和退出标准，必须是可实现的。
课程目标 After completing this lesson, you will be able to:
Define the scope of testing
Determine your test approach
Determine when to start testing and when the testing is complete
学完这一课后，你将能够：
界说测试范畴 确定你的测试要领 确定何时开始测试以及何时完成测试
Throughout this course, you will have an opportunity to gain hands-on practice with various software test activities. We will use the following fictional scenario to provide context for our examples and exercises.
在整个历程中，你将有时机得到种种软件测试运动的实际操纵。我们将使用下面的虚构场景，为我们的例子和练习提供场景。
Project background The Arizona Weather Watcher group is a volunteer organization of professional and amateur weather watchers across Arizona. They hold biannual meetings to share ideas and observations.
项目配景
亚利桑那州的气候视察组是由亚利桑那州的专业和业余的气候视察家志愿者组成的。他们一年举行两次聚会会议，来交换想法和意见。
The Arizona Weather Data Project At the last meeting, it was determined that the group would attempt a long-standing goal. Since the group"s inception, there has been a strong desire to amass a continuously updated database of weather data for all of Arizona. The Weather Watchers have decided that, with the Internet providing easy access, the time is right to attempt this project.
亚利桑那州的气象资料项目
上一次聚会会议确定了该小组将实验一个长期目标。从小组创建以来，积聚所有亚利桑那州的天气数据成为一个不绝更新的数据库的强烈愿望及一直存在。天气视察家决定，既然互联网提供了方便，那么是时候实验这个项目了。
The web tool they want to create will enable group members across Arizona to submit their local weather observations to a central database. This project is called the Arizona Weather Data Project. Many of the examples and exercises in this course refer to this background material. 他们想创建的网络东西，可以使整个亚利桑那州小组的成员能够提交本地天气视察的数据到一其中央数据库。这个项目就被称为亚利桑那州气象数据项目。
许多这个课程中的例子和练习是指此配景。
Throughout this module, you will be documenting your Test Plan for the Arizona Weather Data Project using the Rational Unified Process (IRUP) Master Test Plan Microsoft Word template available on the download page.
在这个模块的整个历程中，你将利用在下载页面下现成的 Rational 统一历程（IRUP）Master Test Plan Microsoft Word 模板，记录亚利桑那州气象数据项目的测试筹划。
The Arizona Weather Data Project (AWDP) consists of a web-based tool that allows volunteers across Arizona to submit local weather observations. 亚利桑那州的天气数据项目（AWDP）里有一个基于网络的东西，使得漫衍在亚利桑那州的志愿者可以提交本地的气象视察资料 。
As you learned in Principles of Test Management, you can subdivide a test plan to better manage varying levels of detail and change. Since the Arizona Weather Data Project team is relatively small, you need to create only one test plan.
正如你在测试治理原则中学到的，你可以细分测试筹划，来更好地处理惩罚细节和水平的条理多样性。由于亚利桑那州气象数据项目团队比力小，你只需要创建一个测试筹划。
Sections of this module refer you to the section numbers and section titles from the IRUP Master Test Plan template. 这个模块的部分，指的是 IRUP 主测试筹划模板里的章节数和标题 。
Developing a Test Strategy 制定 一个测试战略 Once the requirements and risks of a project are well understood, the next step in test planning is to detemine the test strategy. The test strategy answers the following questions at a level that is useful to project managers, management, and members of your test teams:
当需求和项目的风险被充实理解后， 测试筹划的下一步是确定测试战略。在对付项目经理，治理人员和你的团队人员是有用的水准上，测试战略答复了一下问题：
Why are we testing?
What do we plan to do and what do we plan not to do?
How will we do our testing?
The development of a test strategy is a multi-step process of analysis: 我们为什么测试？
我们筹划做什么以及不做什么？
我们将如何做测试？
一个测试战略的形成是一个多步调的阐发历程：
Developing a Test Strategy, continued 制定一个测试战略，续
You already learned how to perform Step 1: Analyze Requirements. You learned how to evaluate functional requirements and nonfunctional requirements and how to develop use cases and use-case models. You learned how to refine bad requirements. You also learned how to perform Step 2: Assess Risk.
你已经学会了如何执行第 1 步：需求阐发。你学过了如何评估成果需求和非成果需求，以及如何制定用例及用例模型。你也学过了如何改造不健全的需求。还学习了如何执行第 2 步：评估风险。
In this lesson, you will learn how to do steps 3 through 5 of developing a test strategy as follows:
在这一课，你将学习创建一个测试战略的第三个步调到第五个步调，如下所示：
Step 3: Define the scope of testing
Step 4: Determine your test approach
Step 5: Determine when to start testing and when the testing is complete
In test strategy development, the first (and in some projects the most important) step is to clarify the testing scope for the project.
第 3 步：界说测试范畴 第 4 步：确定你的测试要领 第 5 步：确定何时开始测试和结束测试。
在创建测试战略时，第一个（在一些项目中最重要的）步调是阐发项目的测试范畴。
Defining the Scope of Testing 界说测试范畴
You must clearly define the scope of your testing. Your scope may be determined in part by your team"s responsibility. A large development project may have multiple test teams working on it, each of which is responsible for a different aspect of the project. Even a small project has different levels of test, as described in the module Test Levels and Activities. Your scope includes the levels of test that you cover.
你必须明确界说你的测试范畴。您的范畴可能部分取决于你的团队的责任。你的范畴可能部分取决于你团队的责任。在大型生长项目里，可能有多个测试团队同时事情，每一个小组卖力项目的差别方面。像在测试阶段和运动中描述的一
样，纵然是很小的项目，也有差别水平的测试。你的范畴包罗你卖力的范畴内的测试阶段。
The scope of your testing is also affected by the nature of the project itself. For example, the scope of testing may be smaller for a small service release to an existing product than for a new product. Make testing scope decisions consciously. Decide which features or functions to test, which products or product combinations to test and which not to test. Be sure to use well-informed risk assessments to understand the risk relative to what you are not testing.
您的测试的范畴也受到项目自己性质的影响。例如，对付一个新产物来说，一个已存在产物的一个小办事的测试范畴可能会更小。清晰地决定测试范畴。决定测试哪些成果或特征， 哪些产物或产物组合进行测试了，而哪些没有进行测试。对付与你没有测试的部分相关的那些风险，一定要信息全面的了解和评估它们。
7．Communicating Testing Scope Decision Communicate scoping decisions to the rest of the project team for their understanding, discussion, and agreement. While it may be easier to proceed quickly in cases in which you have immediate agreement, discussions often have the important side-effect of identifying unspoken assumptions that the project team may hold regarding testing. These discussions can also be helpful in identifying the role that project team members expect testing to play throughout the project lifecycle. Examples of questions to discuss include the following: 为了他们的理解，讨论和赞成，要向项目组成员转达与范畴有关的决定。在你们迅速告竣一致的情况下，可以比力容易的进行，讨论对付判定项目组关于测试可能持有的未说出的假设往往有重要的侧面影响。这些讨论也有助于确定项目小组成员在整个项目生命周期中期望包袱的脚色。讨论的问题例子包罗以下内容：
? Will developers be expected to prove they have done a certain amount of unit testing before they can submit code?
? Is the project manager expecting to supplement the test team with contractors or developers during times of schedule pressures?
开发人员被期望能够证明他们已经做了一定量的单位测试，才可以提交代码吗？
当项目时间压缩时，项目经理希望给测试团队增补合约人大概开发人员吗？ The process of communicating testing scope decisions sets appropriate expectations, in advance, for what testing and the test team can and cannot do for the project. These issues are best discussed in advance, rather than at the time of a crisis or conflict.
在通信测试范畴决定的历程里设置适当的预期，更进一步，预期测试和测试团队对付这个项目，什么可以做什么不能够做。这些问题最功德先讨论，而不是直到危机或辩论的产生了才去讨论。
8. Identifying Scope: Test Levels and Focus Areas 确定范畴：测试阶段和 重点 区域 You can categorize testing activities into levels, with each level focused on an aspect of the application or code. Each level is responsible for a set of focus areas; you need to analyze and assess these focus areas as part of determining the testing strategy. 您可以凭据每个阶段对付应用和代码的偏重方面把测试运动分类成阶段。每一阶段卖力一系列重点领域，你需要把阐发和评估这些重点领域作为确定测试战略的一部分。
9 9
Functional Verification Test Focus Areas 成果验证测试重点领域
The set of focus areas for Functional Verification Testing (FVT) are: 成果验证测试（ FVT ）的重点领域设置：
10
System Verification Test Focus Areas 系统验证测试重点领域
The set of focus areas for System Verification Test (SVT) are: 系统验证测试（SVT）的重点领域设置：
You"ll notice that some of the same focus areas appear for both FVT and SVT. The emphasis, however, is different in each case. Let"s look at the Regression focus area. The FVT team regression tests individual functions, such as login. The SVT team regression tests the system as a whole. For example, the SVT team might rerun load and stress tests.
你会发明，同样的一些重点领域会在 FVT 和 SVT 里同时出现。，但是重点是，在每种情况下是差别的。让我们来看看回归重点领域。FVT 事情组对个别成果进行回归测试，例如登录成果。
SVT 团队的回归测试是测试整个系统。例如，SVT 的团队可能再次执行的负载和压力测试。
11 ．
Test Inclusions
测试 包罗的 运动
Once you have determined the scope of your testing, you are ready to document the scope. Open the IIRUP Master Test Plan template you downloaded earlier in this module and review sections 1.2 and 4.
Section 1.2: Scope Use this section to define the levels of test that you will perform, as well as the levels of test you will not perform. Be sure to review section 4 prior to completing section 1.2 to avoid duplicating information or presenting it in the wrong location.
Section 4: Overview of Planned Tests Use this section to document the features and attributes that you plan on testing. (We will document features that you do not plan on testing later in this lesson.)
一旦你决定了你的测试范畴，您就可以记录你的范畴。打开在本模块中你早些时候已下载的 IIRUP 主测试筹划模板，回顾第 1.2 和第 4 部分。
第 1.2 节：范畴
利用本部分界说你将要执行的测试阶段，以及不执行测试的阶段。一定要事先温习第 4 部分完成第 1.2 节，以制止重复信息或出现在错误的位置。
第 4 部分：回顾测试筹划 使用此部分记录你筹划测试的的成果和属性。（在这一课的背面，我们将记录你禁绝备测试的成果。）
Section 4.1: Outline of Test Inclusions A good way to document test inclusions is to use the results of the risk analysis produced earlier in the planning process.
For the AWDP Test Plan, you can use the table that you created in the Test Planning and Risk Analysis module almost directly. Add one column titled "Additional Information" to capture the logic behind the analysis. Use the new space to explain why a certain feature or attribute was given a particular impact level and likelihood so that a reviewer understands and can evaluate the assessment.
Click on Test Inclusions for an example. 1 4.1 节：测试包罗运动的大纲 一个记录测试运动的好步伐是利用之前在筹划历程中产生的风险阐发的结果。
对付 AWDP 测试筹划，你险些可以直接使用你在测试筹划和风险阐发模块中创建的表格。添加一名为“增补信息”的列，捕获阐发背后的逻辑。使用这块新
空间，来解释为什么某些特征或属性被赐与了特别的影响水平和可能性，以便审阅者能够理解和评价评估。
点击测试运动，举一个例子。
12．
Test Exclusions 测试排除
Section 4.2: Outline of Other Candidates for Potential Inclusion
There may be some features or attributes that you suspect need to be tested but will require more investigation or insight. List those in this section using the same format as test inclusions, but use "Additional Information" as a place to document the reasons why this feature or attribute is considered under potential inclusion.
第 第 4.2 节：其他候选的 潜在运动的 大纲
可能有一些成果或属性，你觉得可能需要进行测试，但将需要更多的视察和了解。在本部分中使用与测试包罗运动相同的格式列出它们，但要使用“增补信息”一列记录为什么此成果或属性被列入潜在运动的原因。
Section 4.3: Outline of Test Exclusions These are features or attributes that you have determined have a low enough priority to accept the risk of not developing and executing tests. Use the "Additional Information" column for the justification to exclude this testing. For example, in the Arizona Weather Data Project application, there is a "Save Draft" option on the data submission form. A possible justification for not testing the "Save Draft" option is the fact that the form does not take very long to complete, and most users would finish entering their observations without the need to save their work along the way.
Click on Test Exclusions for an example.
3 4.3 节：
测试 排除大纲
有些成果或属性，你已经确定它们具有足够低的优先度，可以不生长和执行测试。使用“增补信息”的列解释为什么不需要进行测试。例如，在亚利桑那州气象数据项目应用中，有一 个“生存草稿”的资料提交表单选项。不对 “生存草稿”进行测试的公道理由是，该表不需要很长时间才华完成，并且大多数用户无需一直生存他们的事情就可以完成视察数据的输入。
点击试验排除的一个例子。
13
Determining the Test Approach
确定测试要领
The next step in the process of defining your strategy is to determine your test approach. 确定战略进程的下一步是要确定你的测试要领
14
Determining the Test Approach, continued
确定测试要领，继承
For effective testing, the challenge is to take the prioritized list of features and attributes that were developed based on risk mitigation and assess them against the list of test focus areas, making sure to cover all of the areas.
为了有效的测试，面临的挑战是采取成果和属性的优先级列表，优先级列表是基于风险缓解和对重点领域的测试评估，并且要确保涵盖所有领域。
Recall that the focus areas for Functional Verification Test are:
? Mainline functions
? Error conditions
? Recovery
? Basic usability
? Accessibility
? Global enablement
? Vulnerability
? Regression
追念一下，在成果验证测试的重点领域是：
主线成果 错误条件 规复 根本可用性 可用性 全球可用 漏洞 回归 The focus areas for System Verification Test are:
? Load and stress
? Regression
? Recovery
? Migration
? Usability
? Serviceability
? Functional completeness
? Hardware and software interaction
系统验证测试的重点领域是：
负载和压力 回归 规复 迁移 可用性 使用能力
成果完整性 硬件和软件的相互作用
整理到这里
Taking this approach allows you to concentrate the testing effort to deliver the most benefit. For each of the features and attributes, ask these questions to determine the test approach: ? What testing is planned for this feature or attribute? When answering this question make sure to ask it for each of the focus areas in your test level. For example, does this feature need to be tested for global enablement? Does this feature need to be stress tested? Is this a feature that is likely to be vulnerable to hackers?
? What customer problem does this feature solve? This will help you decide where to focus the testing for this feature.
? What announcement claims will you be making about this feature? This question will help ensure that you are verifying what marketing is saying.
? Will this feature be verified by the execution of the regression tests only? If so, why?
? What automation will be used to develop the tests for this feature? Remember that time and resource will have to be factored into the plan for designing/developing the automation and potentially learning new tools.
You may want to add questions to this list that are specific to your environment. The important thing is to have a list so that you do not miss important considerations.
采取这种要领可以让您专注的测试事情，以提供最大的利益。对付成果和属性，每年提出这些问题，以确定测试要领：
是什么样的测试筹划在此成果或属性？答复这个问题时，请务必请在您的测试级别的重点领域来进行。例如，此成果需要为全球启用测试？此成果需要的压力测试？这是一个成果，很可能会受到黑客的打击？
客户的哪些问题此成果解决？这将有助于您决定在那边会合对这一成果的测试。
通告要求什么，你又对这项成果？这个问题将有助于确保您正在核实营销是说什么。
此成果将被核实的回归测试执行罢了？如果是这样，为什么？
什么自动化将用于开发此成果的测试？请记取，时间和资源将被纳入筹划之内设计/开发的自动化和潜在的学习新的东西。
您可能需要添加到这个列表的问题是特定于您的情况。重要的是有一个列表，以便您不会错过重要的考虑因素。
15 Different Test Levels, Different Test Strategies 差别的测试级别，差别的测试战略
The scope for your Arizona Weather Data Project (AWDP) Test Plan includes two different levels of test: Functional Verification Test (FVT) and System Verification Test (SVT). Different levels of test can require different test strategies.
Let"s look at an example for each of these levels: FVT and SVT. We will use features and attributes from the prioritized list that we developed in the Test Planning and Risk Analysis module. 您的亚利桑那州气象数据项目（AWDP）测试筹划的范畴包罗两个差别条理的测试：成果验证测试（FVT）和系统验证测试（SVT）的。差别级别的测试可能需要差别的测试战略。
让我们来看看为各层级的例子：FVT 和 SVT。我们将使用优先列表，我们在测试筹划和风险阐发模块开发的成果和属性。
16 Example: Test Approach for the AWDP Login Feature 例如：测试的 AWDP 登录成果的要领 One of the high-priority line items for the AWDP is the "login" feature. The basic functionality of the login feature will be tested as part of FVT. You can use an outline like the one below to gather the information you need to document your test approach in your Master Test Plan. In this example, the answers to the questions What testing is planned for this feature or attribute? and What automation will be used to develop the tests for this feature? are captured under the heading Approach to Testing. The answer to the question What customer problem does this feature solve? under the heading Overview or Brief Description.
Recall that your test approach should address situations that are specific to your environment. In this example, the fact that the authentication function is using services provided by another group is called out under the heading Assumptions/Issues Specific to this Feature.
高优先事项 AWDP 行项目之一是“登录”成果。在登录成果的根本成果将受到考验，作为 FVT 的一部分。您可以使用类似下面这一收集需要的信息记录你对你总
的测试要领测试筹划纲领。
在这个例子中，对什么进行测试，此成果或属性的筹划问题的答案？和什么自动化将用于开发此成果的测试？被捕获的标题下的测试要领。对这一问题的客户的哪些问题不解决这一成果的答案？的标题下概述或扼要说明。
追念一下，您的测试步伐应处理惩罚的特殊情况对您的情况。在这个例子中，一个事实，即验证成果是由另一组使用所提供的办事被称为假设项下出/这一问题的具体特征。
Feature Name: Login
Lead Developer: Sue Lead Function Tester: Javier Lead System Tester: Thelma Overview or Brief Description: A user is required to log in using their registered userid (email address) and password. Approach to Testing: Develop a set of automated tests to test the ability to log in valid users that are registered. Drive error paths by logging in with invalid userids and passwords. Assumptions/Issues Specific to this Feature: Authentication using the userid and password is provided by an external service that will be called. It is assumed that this function already has been thoroughly tested and supported. We will not do vulnerability testing on entering userids and passwords.
成果名称：登录
铅开发商：苏
铅成果测试仪：哈维尔
铅系统测试仪：塞尔玛
概述或扼要说明：用户需要登录使用其注册用户名（电子邮件地点）和密码。
测试要领：制定了一套自动化测试，测试的能力，有效用户登录注册的。在使用无效的用户id 和密码记录器的错误路径。
假设/这个问题的具体特征：身份验证使用用户 ID 和密码是由外部提供办事，将被调用。据推测，这一职能已经过彻底测试和支持。我们不会在进入用户 id 和密码的漏洞测试。
17 Exercise 1: Test Approach for Concurrent Users Feature 练习 1：测试要领为特征并发用户 Another of the requirements for the AWDP system is that 1500 users can access the tool concurrently. This attribute will be tested as part of SVT. 在对 AWDP 系统的要求另一个原因是，1500 用户可以访问该东西同时进行。此属性将被测试作为 SVT 的一部分。
19
Documenting the Test Approach 记录的测试要领 Section 5 of the IIRUP Master Test Plan provides you with a template for documenting your test approach. Section 5 includes these headings:
5.1 Measuring the Extent of Testing 5.2 Identifying and Justifying Tests 5.3 Conducting Tests
The IIRUP template is just that, a template. Teams modify the template to suit their needs. For a small project, you may choose to document your test approach by line item or feature as shown in the screen capture.
As you can imagine, this level of detail would quickly become cumbersome for a large project. A better approach for a large project is to manage this detail in a spreadsheet. In this case, the test plan includes a high level overview of the test approach with a reference to the more detailed spreadsheet. Creating feature or iteration test plans in addition to the Master Test Plan can also be very useful for a larger project.
科 IIRUP 主测试筹划 5 提供了一个模板，用于记录您的测试要领。第 5 节包罗以下标题：
5.1 测水平测试
5.2 中说明和测试
5.3 进行测试
该 IIRUP 模板的只是，一个模板。团队修改模板以适应他们的需要。对付一个小项目，你可以选择你的文件按项目测试要领或成果如屏幕捕获所示。
你可以想象，这种详细水平将迅速成为累赘一项庞大的工程。一个大型项目的更好的要领是，以治理电子表格这一细节。在这种情况下，测试筹划包罗一个以电
子表格的更详细的参考测试要领高条理的概述。创建成果或除主测试筹划的迭代测试筹划也可以是非常有用的一个较大项目。
20 Determining Entry and Exit Criteria for Testing 确定进出境查验标准 As part of the test strategy, you determine when to start testing by identifying Entry Criteria and when the testing is complete by identifying Exit Criteria. 作为测试战略的一部分，您决定何时首先确定入学标准和测试时，通过识别出口标准的完整测试。
21 What do Entry and Exit Criteria do for You?
Entry Criteria and Exit Criteria answer the following questions:
? As a product moves through the development process, can the tests that we have defined for each level or iteration be executed in an effective and efficient manner?
? How will we know when are we finished testing a particular level or iteration?
In order for entry and exit criteria to be effective, they must have three common attributes:
? Entry and exit criteria must be meaningful.
o Each criterion should exist for a specific reason.
o A cause and effect should be shown or implied.
o They should aid in risk assessment.
? Entry and exit criteria must be measurable.
o If it cannot be measured, it is not useful.
o It should never be subjective.
o The status is calculated using empirical data.
? Entry and exit criteria must be achievable.
o The criteria must be realistic, not unobtainable.
Never carry forward a criteria that has never been met; it dilutes the effectiveness of the other criteria. 入学标准和退出条件答复下列问题：
通过生长进程中的产物移动，我们可以为每个级别或迭代界说的测试执行有效和高效的方法？
我们如何知道我们完成测试某个特定水平或迭代？
在进入和退出条件才华有效，就必须有 3 个配合的属性：
进入和退出标准，必须是有意义的。
每个标准应该存在的具体原因。
因果应表明或体现。
他们应该资助风险评估。
进入和退出标准，必须是可权衡的。
如果它不能权衡，它是没有用的。
它不应该是主观的。
状态为盘算经验数据。
进入和退出标准，必须是可以实现的。
该标准必须是现实的，不是不能实现的。
从来没有发扬一个从未到达的标准，它淡化了其他标准的效力。
22 Determining Entry Criteria 确定入学标准 When determining entry criteria, document what is required by a team to begin testing and proceed efficiently and effectively with a manageable amount of risk. The criteria should be discrete and easily measured. They should also be used to determine an acceptable amount of risk. For example, ask the question: If these criteria are not met, what could happen and what would the result be? Assign a risk assessment value to each criterion. Refine this value over time and is use it to identify productive recovery actions. When determining risk, it is important to total the individual risk assessment values to get a complete understanding of the entire situation. The risk determination is important because if an entry criterion is not met, it does not mean that the test organization stops working. 在确定入学标准，文件什么是需要一个团队开始测试和进行有效的风险管控的有效。该标准应是离散的和容易权衡。他们应该也可以用来确定一个可担当的风险金额。举例来说，提出这个问题：
如果这些条件得不到满足，会产生什么和什么结果呢？
指定一个风险评估值为每个标准。随着时间改造此值，并用它来确定生产规复操纵。在确定风险，重要的是总的小我私家风险评估的代价得到了整个局势的全面了解。风险的决心非常重要，因为如果一个项目不切合标准的，但这并不意味着测试机构停止事情。
Entry criteria being met is really a checkpoint that shows the overall status of a product. Higher levels of risk indicate that the testing may not be optimally effective, which increases the risk that targeted problems will escape to the field. For example, if some of the planned functionality is not delivered on schedule, the risk is increased as the amount of time available to test that functionality is reduced. The risk is increased further if testing of other planned functionality is dependent on the piece that is delayed. Once the team understands the objectives, you can ask the following question to start establishing good entry criteria: For entry criteria, what has to have happened so that we can begin, be effective and efficient, and proceed with a manageable amount of risk? 入 学条件得到满足实在是一个查抄点，显示了产物的整体状态。风险水平较高的测试表明，就不能很好的效益，从而增加有针对性的风险问题，将逃往外地。例如，如 果筹划中的某些成果不能如期交付的风险有所增加的时间来测试该成果数额淘汰。风险是进一步增加，如果筹划中的其他成果测试是在这片延迟依赖。
一旦球队了解的目标，可以提出以下的问题开始创建良好的入学标准：
入境标准，有什么事情，以便我们能够开始，是有效的和有效率，并进行风险治理的数额？
23 Evaluating Ideas for Entry Criteria 评价理念的入学标准 As the team brainstorms, list ideas for potential entry criteria. Assess each idea and make sure that it is meaningful, measurable, and achievable.
Example 1: A member of the team suggests that, as an entry criterion, "A specific set of variations defined in an earlier test level must run successfully."
Make sure that you can defend why these variations must run and quantify the risk of continuing should any of them fail. Avoid ambiguous criteria such as "Function Test must be 80% complete." This criterion is ambiguous because it does not specify which 80% must be complete. Also, if there are a lot of tests, the failing 20% could impact your ability to make progress. It is better to specify which variations must execute successfully.
随着球队的奇思妙想，为潜在的入学标准清单的想法。评估每个想法，并确保它是有意义的，可丈量的和可以实现的。
示例 1：对小组成员发起，作为项目的标准，“一个在早些时候测试级别的界说必须乐成运行一套具体的变革。”
请 确保您可以掩护这些变革的原因必须运行和量化应继承他们任何失败的风险。制止出现诸如“成果测试，必须完成 80％暗昧的标准。”这一标准是模糊的，因为它 没有具体说明，其中 80％必须是完整的。别的，如果有许多的测试，20％失败的可能影响您的能力取得进展。这是更好地指定的变革，必须乐成执行。
Example 2: A member of the team suggests that, as an entry criterion, "A specific set of tests, sometimes called an acceptance test, must be executed successfully."
Make sure that you can defend each of the tests and can quantify the risk of continuing should a given test fail. Example 3: A member of the team suggests that, as an entry criterion, "The test plan must be reviewed and approved."
Make sure that you can defend why the test plan must be approved, and can quantify the risk to the test if the plan is not approved.
例 2：对小组成员发起，作为项目的标准，“一组特定的测试，有时也被称为的验收，必须执行的乐成。”
确保您能保卫每个测试和可量化的连续应给定的测试失败的风险。
例 3：对小组成员发起，作为入门标准“的测试筹划必须经过审查和批准。”
请确保您可以掩护为什么测试筹划必须得到批准，可以量化的风险的考验，如果筹划未获批准。
24 Determining Exit Criteria
确定退出标准 When determining exit criteria, identify what must be accomplished for the test effort to be complete for a particular test level or iteration. Agree up front with the project manager what needs to be done for the test effort to be complete. Remember that you must state the goals and objectives in measurable terms. Associate meeting your exit criteria with another aspect of the project. For example, associate the system test exit with a product ship decision or customer entry criteria. That will cause others outside of your team to feel a sense of urgency to ensure that your exit criteria are met. It will also help you to justify requests for help where needed. Once the team understands your testing objectives, you can ask the following question to start establishing good exit criteria: How do we know when we are done?
在确定退出标准，确定哪些必须为测试事情完成的针对特定测试级别或迭代完成。同意与项目经理所需要做的测试事情完成前要完成。请记取，你必须明确的目标和可丈量的目标。
副访问该项目的另一个方面，你的退出条件。例如，系统关联的产物或客户决定船舶入出境的标准测试。这将导致你的团队以外的其他人感触一种紧迫感，以确保您退出条件得到满足。它还将资助您在正当理由需要资助的请求。
一旦球队明白你的测试目标，可以提出以下的问题开始创建良好的退出标准：
我们怎么知道我们什么时候完成？
25 Evaluating Ideas for Exit Criteria 评价标准的退出思路 As the team brainstorms, list ...
热点文章阅读