集成测试是一个笼统的术语吗？如果是，它包括什么类型的测试？ [英] Is integration testing an umbrella term and if so, what types of tests does it include?

问题描述

我发现集成测试的概念令人困惑。似乎有很多解释和范围：

I find the concept of 'integration testing' confusing. There seems to be quite a few explanations and scopes:

• 功能/验收测试（例如测试用户界面）例如，使用Selenium）


• 将不同类/模块的软件集成在一起测试（只需将两个或多个类一起测试，而无需做任何特殊的事情，例如数据库调用和内容）


• 测试系统配置功能/功能独立（数据库集成有效，依赖项已正确注入，安全基类正常工作）


• 测试整个系统（运行使用数据库，Web服务等的服务）


• 等。等等。

• 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.

我开始将集成测试视为一个笼统的术语（与在编程讨论中定义特定/严格含义相反）通常被赋予它）：

I begin to see integration testing as an umbrella term (as opposed to defining it in programming talks, where specific/strict meaning is often given to it):

• 集成测试包含：
  
  
  
  
  • 单元集成测试（测试同一包中不同类的集成，而无需调用外部库）
  
  
  • 功能/接受度测试（例如，通过Selenium测试软件的最终输出）
  
  
  • 系统测试（包括各种与技术和功能无关的更广泛的测试测试维基百科文章）
  
  
  • 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默认生命周期中，只有测试和集成测试阶段。这似乎将测试大致分为两类，并且符合这些假设。

    In Maven default lifecycle, there is only 'test' and 'integration-test' phases. This seems to split the tests into roughly two categories and would go along with these assumptions.

    有很多现有的问题和答案试图寻找单元测试，功能测试，回归测试等。但是，我正在寻找有关集成测试的更具体答案：如何对集成测试进行分类，以及其中包含什么？另外，您是否像我一样将软件测试大致分为两类：单元测试（1个单元）与集成测试（2个以上单元）？

    There are many existing questions and answers looking for differences between unit testing, functional testing, regression testing, etc. in general. However, I am looking for more specific answer regarding integration tests: how do you categorize integration testing and what do you include inside it? Also, do you shun splitting software testing roughly into two categories as I have done: unit tests (1 unit) vs. integration tests (2+ units)?

    推荐答案

    我们的团队（用您的话说）认为集成测试涵盖了

    My team sees (using your words), integration testing as covering

    
    
    • 测试不同类/的集成/软件模块在一起（只需一起测试两个或多个类，而无需执行任何特殊的操作，如db调用和填充）
    
    
    • 测试系统配置功能/功能独立（数据库集成有效，依赖正确注入，安全性基类就可以工作）
    
    

    没什么。我们将系统测试和验收测试视为不同的系列。

    and nothing else. System tests and acceptance tests we see as different families.

    我们对此进行了长时间的讨论，以确保在谈论测试时我们都说相同的语言。 。

    we had some lengthy discussions on this, to make sure that we were all speaking the same language when we talked about tests.

    我并不完全反对您定义为集成测试的内容，但是我只是说，如果您与之一起工作的所有人都同意，分类。

    I'm not strongly disagreeing with what you define as integration tests, but I'm just saying that it's nice if all the people you're working with agree on a classification.

    这篇关于集成测试是一个笼统的术语吗？如果是，它包括什么类型的测试？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！