对于那些下载了我们最新的测试分支，目前正在使用它，你会自动删除，并将其放在默认版本。
For those who downloaded our most recent beta branch and are currently using it, you'll be automatically removed from it and put on the default version.
如何在开发中的主干运行持续集成(Continuous Integration,CI)，以定期测试分支与主干的合并？
How to run Continuous Integration (CI) against a branch that is under development and regularly test the merge against the trunk?
有时它会被引用作为不同的分支、路径，或者变异性识别，在测试设计者识别各种方法的所有用例中，用户或者外部的系统都可以执行这个用例。
While it is variously referred to as branch, path, or variability identification, in all cases the test designer identifies the various ways the user or external system can execute the use case.
您必须在编写每个测试时尽量地覆盖尽可能多的方法和分支。
You have to write each test to cover as much as it possibly can.
除了对静默输出风格的直接利用以外，这个分支还举例说明了相对于测试套件的自定义测试以及对结果报告的控制。
Aside from the direct utility of the quiet output style, the branch illustrates custom testing against test suites and control of result reporting.
每个分支、循环，或其他逻辑在加入源代码之前都要写出将要执行结果的自动化测试。
Each branch, loop, or other logic added to the source code is preceded by the writing of an atomic test that will exercise that outcome.
单个的分支开发和增量的的检入只有在频繁地执行自动化的构建和测试时才能够实行。
Single branch development and incremental check-in can only work when automated builds and tests are executed frequently.
只要测试通过，修改的部分就可以推送到主分支。
Once the tests have been passed the change set is pushed to the main branch.
团队分支是红色的，表示它不太稳定；例如：这个分支通过了单元测试，但是它可能还没有完成集成测试，所以还没有稳定到可以发布的状态。
The team branch is red to highlight that it is less stable, i.e. the stuff on that branch passes the unit tests but it might not be integration tested and might not be stable enough for release.
除此之外，测试的分支建模将导致由于完成不同功能的测试具有相似的名称所带来的混乱。
Furthermore, the branching model for tests results in similarly named tests that have different functionality to the confusion of everyone.
当有人考虑从工作分支向主干发布代码时，要触发该手工测试，以检查故事是否“完成”。
This test is triggered manually whenever someone is considering to publish code from work to trunk, as a way to check that the story is Done.
代码覆盖工具可报告测试覆盖率——以行覆盖或分支覆盖形式表示——它表示测试运行时所涉及的代码量。
A code coverage tool reports test coverage — either in the form of line or branch coverage — that represents the amount of code that is being touched when a test is run.
对每个工作分支来说，CI服务器自动并有规律地(如果不能持续地)运行集成测试和回归测试。
For each work branch, CI server automatically and regularly (if not continuously) runs integration tests and regression tests.
条件寄存器(ConditionRegister,CR)是反映特定操作结果并提供测试(及分支)机制的32位寄存器。
The Condition register (CR) is a 32-bit register that reflects the result of certain operations and provides a mechanism for testing (and branching).
然而，你也可以将NUnit的[testfixture]看作是组织测试包的一种方法，它将测试包组织为每个类，形成treeview的每一个分支。
However, you can also think of NUnit's [TestFixture] as a way of organizing a test suite as each class forms an individual branch in the treeview under the name of the project.
当每个方法都有了至少一个测试，使用一个代码覆盖率工具如cobertura为每个分支编写一个测试，直到每一行代码都能够被测试。
Once every method has at least one test, use a code coverage tool, such as Cobertura, to write one test for every branch until each line of code is tested.
与行覆盖一样，如果在特定方法中有两个分支，并且两个分支在测试中都被覆盖，那么您可以说这个方法有100%的分支覆盖率。
Just like line coverage, if there are two branches in a particular method and both were covered through tests, then you could say the method has 100% branch coverage.
由于每个团队都要在发布代码到主干前进行测试，因此他们有各自的工作分支。
Each team has their own work branch, since they each need somewhere to test their code before publishing to the trunk.
由于不同的阶段发生在不同的时间，同样的编码人员、业务分析师或是测试人员不需要再当前的分支的每个阶段被100%的利用是可行的。
Since the different phases occur at different times, it's feasible that the same coder, business analyst, or tester won't be 100 percent utilized at each phase of the current branch.
我引入了动态脚本来支持HTTP测试脚本中的分支、循环和自定义验证。
I introduced dynamic scripting to allow branching, looping, and custom validation in HTTP test scripts.
您能确定每个方法都被测试到、每个分支都进入过么？
Are you sure that every method is tested and every branch followed?
对每个工作分支来说，CI服务器自动并持续地检查构建和运行所有单元测试的状况。
For each work branch, CI server automatically and continuously checks that it builds and passes all unit tests.
这个报告表明，虽然从总体上说该方法被测试到了，但实际上还有许多分支没有测试到。
This report reveals that although the method as a whole is tested, many branches are not.
只要这个故事相关的代码在工作分支上完成实现并通过测试，我们把所有的相关内容从工作分支上复制到主干上就可以了。
As soon as a story is implemented and tested on the work branch we copy everything from work to trunk.
然而，所涉及到的许多分析问题是类似的，并且对于控制工程的所有分支来说，大多数的分析、综合技术与测试方法都是相同的。
However, many of the analytical problems involved are similar and most of the techniques of analysis and syntheses and methods of test are common to all branches of control engineering.
Cobertura通过被测试的行数和被测试的分支数来计算覆盖率。
Cobertura calculates coverage both by the number of lines tested and by the number of branches tested.
else代码块是一个简单的逻辑分支，根据测试期望说明选取一条路经——而不是另一条路经——之后测试将失败(或通过)的原因。
Else code block is a simple logical crossroad that helps show why the test would fail or pass if one path - and not another - is taken, according to test expectations.
Equinox 3.5已经部分支持OSGi 4.2了，ApacheFelix在上月初也已经通过了一个测试集(在4.2规范发布前)。
Equinox 3.5 already provided some of the OSGi 4.2 support, and Apache Felix had a passing test set earlier on in the month (prior to the 4.2 spec being passed).
编码压缩技术作为测试数据压缩方法的一个重要分支，已被广泛采用。
An important branch of compression method is to encode test data and that is used widely.
编码压缩技术作为测试数据压缩方法的一个重要分支，已被广泛采用。
An important branch of compression method is to encode test data and that is used widely.
应用推荐