您可以在不创建测试代码的情况下执行单元/集成测试吗？
在我们的项目中，测试程序和预期测试结果（测试规范） 是在文档中创建的。 然后，我们对构建的产品/版本进行测试。 这里不涉及测试代码和测试工具。
这对于单元/集成测试来说可以接受吗？
In our project, test procedures and expected test results (test specifications)
are created in a document.
Then, we perform testing on a built product / release.
Here, no test codes nor test tools are involved.
Is this acceptable for unit / integration testing?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
您正在做的是“手动测试”。
每个定义的手动测试不是，也永远不可能是单元测试。
手动测试可以用于集成测试，实际上应该在某种程度上使用，因为自动化测试无法发现所有形式的意外错误情况。特别是与布局和“看起来不正确”的事情有关的错误（这在网络应用程序中很常见）。
但是，如果您根本没有自动化测试，则意味着您的应用程序没有经过充分的测试。因为手动测试每个版本的应用程序的每个详细方面是完全不可行的 - 没有组织愿意或能够支付所需的费用。
What you are doing is "manual testing".
Manual testing per definition is not, and can never be unit testing.
Manual testing can be used for integration testing, and in fact should be used to some degree, because automated tests cannot spot all forms of unexpected error conditions. Especially bugs having to do with layout and things not "looking right" (which happen to be rather common in web apps).
However, if you have no automated tests at all, it means that your application is insufficiently tested, period. Because it's completely infeasible to manually test every detailed aspect of an application for every release - no organization would be willing or able to pay for the effort that would require.
不，你所描述的既不是单元测试也不是集成测试，它是在街区周围散步去喝杯咖啡。
No. what you describe is neither unit nor integration testing, it is taking the build for a walk around the block to get a cup of coffee.
据我了解，单元测试是对各个代码单元的测试。级别相对较低，通常与代码本身同时开发。
为此，您还需要使用代码，并且最终执行这些测试的代码是测试工具，即使由于某种原因您没有使用框架。
所以不，如果您不使用测试工具或测试代码，那么您就没有进行单元测试。
理论上，您可以手动进行集成测试，但它仍然不可靠，因为人往往会不一致并且成本高昂，因为人比机器慢。
最终，您可以自动化的测试越多，您的测试就会越快、越准确，您的 QA 人员就越能自由地测试只能手动测试的内容。
Unit testing is - as I understand it - the testing of individual units of code. Relatively low level and usually developed at the same time as the code itself.
To do that you need to be working in code as well and ultimately the code that performs these tests is testing tool even if for some reason you aren't using a framework.
So no, if you aren't using testing tools or testing code, you aren't doing unit testing.
Theoretically you could be doing integration testing manually, but it's still unreliable because people tend to be inconsistent and expensive because people are slower than machines.
Ultimately the more testing you can automate, the faster and more accurate your tests will be and the more you will free your QA personel to test things that can only be tested manually.
单元测试和集成测试是两个截然不同的事情，什么构成“可接受”完全取决于您的组织。测试系统而不是单独测试每个单元很可能是可以接受的。
就我个人而言，我不喜欢自动化单元测试，因为我遇到的绝大多数问题都是只有在系统测试的情况下才会出现的问题。
我倾向于逐步开发，这样随着我正在开发的内容的增长，它就会成为自己的测试工具，并且在构建任何东西之前，基础都会被证明是坚实的。
我希望能够自动化系统测试。它揭示了我在一百万年编写单元测试中从未想到的所有事情。
Unit and Integration testing are two very different things, and what constitutes "acceptable" depends entirely on your organisation. It may very well be acceptable to test the system, rather than each unit separately.
Personally, I'm not a fan of automated unit testing, since the vast majority of issues I encounter are the sort of things that only ever come to light in the context of a system test.
I tend to develop incrementally, so that as what I'm working on grows, it becomes its own test harness, and foundations are proved to be solid before building anything on them.
I'd love to be able to automate system testing. It reveals all the things I would never have thought of in a million years of writing unit tests.