注意你的结果依据你记录测试的时间不同将有所变化。
Note that your results may vary depending on when you record your test.
你的测试是特别的，没有任何记录，也没有任何东西需要自动化。
Your testing is AD hoc, nothing is written down, and there's nothing to automate.
然而，使用IBMRationalManualTester，你可以构件的测试集合起来，这些构件记录了测试应用软件一小部分区域的步骤集。
However, with IBM Rational Manual Tester, you can assemble tests from components that document a set of steps for testing a small area of the application.
把你测试需要用到的任何场景、数据都记录下来。
Note any scenarios and/or data that you will need to test with.
所以快点行动，经常测试，快速失败，讨论并用文件记录你的假设。
So move quickly, test often, fail fast, and discuss and document your assumptions.
你可以通过拖拽内建的测试库来创建测试而无需应用记录或是测试编程。
Tests are created via drag and drop of built-in test libraries, instead of application recording or test programming.
这些记录同样对于设立新的对比测试项目有重要的参考作用，你可以观察到在每部分中，哪些布局形式和可复制的样式是最具有效率的改动。
This also provides a point of reference for when you are starting new projects –you can see which placements and copy types are most effective in which industries.
你应将每个月的测试通过电子表格进行记录和管理，以避免无意中对同样元素进行反复、多次的重复测试(从而降低了效率)。
Every month you should track your results in a spreadsheet to avoid accidentally re-testing the same elements over and over again.
如果你的手工测试已经在MicrosoftWord或Excel中记录下来了，使用IBMRationalManualTester，你可以批量导入这些内容，开始进行手工测试创建。
If your manual tests are already documented in Microsoft Word or Excel, with IBM Rational manual Tester you can bulk-import the content and jump-start manual test creation.
你也可以安排一些测试以使它们依序执行、按类别组合一些测试以让它们一起运行、记录单元测试所花费的时间，以及其它许多事情。
You can also arrange tests so that they are performed in sequence, group tests by categories and run them together, record the amount of time unit tests take, and much more.
你需要创建和记录测试，管理和维护他们，他们执行并报告结果，以及管理测试环境一个完整的流程和环境。
You need a complete process and environment for creating and documenting tests, managing and maintaining them, executing them and reporting the results, as well as managing the test environment.
在这一课的后面，我们将记录你不准备测试的功能。
We will document features that you do not plan on testing later in this lesson.
打开你的波动软件，对照你的交易记录，用你自己的数据来测试本书的思想。
Open your charting software, pull out your trading records, test all the concepts on your own data.
你是否有可追踪从每个单位的计量和测试设备的相关记录？
Do you have traceability from each unit of measurement and test equipment to the associated records?
你是否有保持校准每个单位的计量和测试设备记录？
Do you maintain records of calibration for each unit of measurement and test equipment?
在测试时，你不希望记录被删除掉，但是你却没有任何阻止的方法。
In your test, you don't want the record deleted, but you don't have any way to stop it.
你需要测试一两个记录来看你存储的数据是否正确。
You will then need to print out one or two records to check the data was stored correctly.
你必须定义需求，测试用例和测试环境。工具只能记录并回放基于操作者的操作行为的活动。
You must define business requirements, test cases and test scenarios. The tool can only record and playback based on what actions the user performs.
你也可以随便下载那些商业键盘记录工具来测试，这些工具大多数都可以免费试用的。
Or you can download any number of commercial keyloggers from sites such as CNet's Download. com for testing. Most of these will have a free trial period.
第二个部分是运行的测试的历史记录，你可以查看这些历史记录，最近运行的一些测试，能够使你查看测试运行的结果。
The second part is the historical test runs, which you can look through and some of the later test runs allow you to check the results of the run.
一旦你明白了，把他们拉要求的测试程序，记录，提高了他们的开发文档。
Once you have figured it out, send them a pull request that improves their developer documentation by documenting the test procedures.
这里要指出一个重点：你应该记录原始分辨率下的页面显示效果，以帮助你在页面测试完毕之后改回原样。
Important note: You may want to make a note of your original resolution so you can change back after experimenting.
构建交易策略，你将需要获得反映交易时间框架的图表、一个好奇且客观的头脑和一打记录想法的纸张。 这些想法可以规范化的使用到策略中并且在其他图表中得到测试。
There are many great trading strategies out there, and purchasing books or courses does save time, but trading can also be a "do it yourself" career.
构建交易策略，你将需要获得反映交易时间框架的图表、一个好奇且客观的头脑和一打记录想法的纸张。 这些想法可以规范化的使用到策略中并且在其他图表中得到测试。
There are many great trading strategies out there, and purchasing books or courses does save time, but trading can also be a "do it yourself" career.
应用推荐