使用“探索性测试”来产生反馈。
特别是如果你不知道选择探索性测试的话。
2002版转向了基于探索性测试的方法。
The 2002 version shows a shift to an approach based on exploratory testing.
从另一方面来说，探索性测试可能更加特殊。
功能测试和探索性测试的区别是什么？
Do you know the difference between functional testing and exploratory testing?
功能性测试和探索性测试的区别是什么？
Do you know the difference between functional testing and exploratory testing?
进行探索性测试的人员需要什么技能呢？
探索性测试的应用范围与测试本身是相同的。
The scope of exploration is the same as the scope of testing itself.
所以这跟探索性测试没有区别，除了发生的时间有点延时而已。
This is no different from exploratory testing except for longer time delays between activties.
基于需求的测试往往没有探索性测试那么主观，它也可以带来其他的益处。
Requirements-based testing tends to be less subjective than exploratory testing, and it can provide other benefits as well.
团队在采用更多自动化回归测试之后，需要测试人员具有精湛的探索性测试技能。
Teams with more automated regression suites need testers with sharp exploratory testing skills.
然后开始疯狂于各种测试：冒烟测试，各种用户验收测试套件，回归和探索性测试。
Then go nuts: smoke tests, any acceptance test suite you have, and of course regression and exploratory testing.
软件开发团队的其他部分可能质疑或者谴责探索性测试的结果，但是他们不能怀疑直接确认需求的测试。
Other parts of the software development team may question or even condemn results from exploratory testing, but they cannot dispute carefully developed tests that directly validate requirements.
如果做到了下一项测试被我们所做的上一测试的结果所影响，那么我们就是在做探索性测试。
To the extent that the next test we do is influenced by the result of the last test we did, we are doing exploratory testing.
另一个好处是它可以更容易地计算所需的测试工作(与探索性测试相反，它总是受限于可以利用的时间)。
Another advantage is that it can be easier to calculate the testing effort required (as opposed to exploratory testing, which is often only bounded by available time).
无论从测试设计角度还是从测试执行角度，脚本化的测试，要想做的足够好，都比探索性测试要难。
Both on the design side and the execution side, scripted testing done adequately is harder than exploratory testing done adequately.
我即将在软件测试协会会议上做的一个报告要问到我们现在所知道的：什么是探索性测试，我们如何进行这种测试？
My upcoming talk to the Conference of the Association for Software testing asks what we know now: what is exploratory testing and how do we do it?
提供相关质量信息，而不是通过自动化测试、探索性测试(exploratory test)[译注]来寻找bug。
Provide information about quality not to find bugs via automated tests, exploratory tests,...
测试人员从而可以专注于进行“探索性测试”，并与ProductOwner一起与客户沟通，并帮助团队理解用户(而不仅仅是故事)。
This frees the testers to do Exploratory Testing, work with the Product Owner to connect with the customer and help the team understand the users (not just the stories).
所有这些人和系统级别的软件测试人员(soft ware validator)一起，才能做好自动脚本测试或者探索性测试。
All of these folks, along with the system-level software validators, can test in a scripted way or an exploratory way.
最近有一种宣传，针对系统测试的与探索性测试相对(完全脚本化)的测试方法，可以阅读LisaCrispin的《极限编程测试》。
For a strong recent example of advocacy of an anti-exploratory (fully scripted) approach to system testing, read Lisa Crispin's testing Extreme Programming.
他觉得Kent只是做了一个探索性的开发(spike)，对Eclipse的插件架构体系进行了了解，并且试图找出如何在那个环境中编写测试。
He believes that Kent was really just doing an investigative spike exploring the eclipse plugin structure and trying to understand how to write tests in that environment.
其中的一些测试是探索性的，甚至有些探索性的测试需要以自动化方式实现，以便以后重复运行。
Some of those tests will be exploratory. Even some of the exploratory tests will need to be automated in order to repeat them.
当我训练一名测试新手时，我都从高度探索性的测试工作开始。
When I am training a new tester, I begin with highly exploratory testing.
本文通过对实际声音识别系统的测试和研究，为进一步开发实用性声音识别系统的工作做了基础和探索性的工作。
This paper makes a basic and preparatory study for exploring practical sound recognition system further by testing and investigating actual sound recognition system.
管理者认为脚本化的测试要比探索性的测试容易，这是因为，他们对测试的质量要求并不高，而对表面上看起来测试是否井然有序以及是否体现了较高的测试生产力，更注重一些。
The reason managers assume it's simpler and easier is that they have low standards for the quality of testing and yet a strong desire for the appearances of order and productivity.
管理者认为脚本化的测试要比探索性的测试容易，这是因为，他们对测试的质量要求并不高，而对表面上看起来测试是否井然有序以及是否体现了较高的测试生产力，更注重一些。
The reason managers assume it's simpler and easier is that they have low standards for the quality of testing and yet a strong desire for the appearances of order and productivity.
应用推荐