我认为,一体化测试的概念混淆不清。 似乎有几个解释和范围:
- Functional/acceptance testing (e.g. testing the user interface with for example, Selenium)
- Testing the integration of different classes/modules of software together (simply testing two or more classes together, without them doing anything special like db calls and stuff)
- Testing the system configuration function/feature-independently (database integration works, dependencies are correctly injected, security base classes work)
- Testing the system as whole (running services that use databases, web services, etc.)
- etc. etc.
我开始将一体化测试视为一个总括性术语(而不是在方案拟定会谈中加以界定,而方案谈判往往对它有具体/有限的含义):
- Integration testing contains:
- Unit integration testing (test integration of different classes within the same package without calling external libraries)
- Functional/acceptance testing (test final output of the software through Selenium, for example)
- System testing (includes various, more technical & non-feature related tests as listed in Wikipedia article)
在Maven省,只有测试和一体化测试阶段。 这似乎将测试分成两个类别,并将与这些假设相配合。
现有的许多问题和答案一般都涉及单位测试、功能测试、回归测试等之间的差异。 然而,我正在寻求关于融合测试的更具体的答复:你如何分类融合测试,以及你在其中的内容? 另外,你是否像我所做的那样,将软件测试大致分为两类:单位测试(1个单位)和集成测试(2个+单位)?