blocks|key|1033782|text|您可以为测试目的定义数据库配置，并连接到实际数据库以执行测试。您应该访问测试类中的测试数据库配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033783|例如，如果使用spring和hibernate连接到数据库，则可以定义测试hibernate配置xml文件，将其连接到测试数据库。然后，在您的测试类中，按照以下方式使用此配置文件：|1033784|@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguratiion({testHibernate.xml,+testSpring.xml+,+....+})
@TestExecutionListeners({...})
public+class+TestClass+{
....
+++@Test
+++public+void+test1(){+
+++++...
+++}
}|code-block|syntax|javascript|1033785|因此，您可以访问测试hibernate会话工厂来执行查询。|1033786|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

you can define database configuration for test purpose and connect to your real database base for execute tests. you should access to test database configuration in test classes.

for example, if you use spring and hibernate to connect to the database, you can define a test hibernate configuration xml file where it connect to test database. then in your test classes, use this configuration file as follow:

<pre><code>@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguratiion({testHibernate.xml, testSpring.xml , .... })
@TestExecutionListeners({...})
public class TestClass {
....
 @Test
 public void test1(){ 
 ...
 }
}
</code></pre>

so, you can access your test hibernate session factory to execute your queries.

blocks|key|2749791|text|您不应该更改您的查询。在测试中，您应该只更改应用程序将使用的连接url。问题是，如何让这个url起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2749792|要获得完整的测试覆盖率，您需要相同的db+(正如您注意到的，h2和其他内存中的db并不完全兼容)。postgres没有内存模式，所以您必须自己管理生命周期。你得做几个决定。其中一些：|2749793|您将从哪里获得数据库:要求所有的开发人员提供postgres+(安装/停靠/游走)或自动化设置？|unordered-list-item|2749794|如何为测试准备db+:手动模式设置和清理？|2749795|如何在测试之间重置db+:重新启动？总是回滚？预定义和单独定义的内容？某种反向操作？|2749796|如果和如何快速完成这些测试？|2749797|有一些工具可以帮助您解决一些问题：|2749798|测试容器将帮助您提供db。|ordered-list-item|offset|length|2749799|迪布尼特+--将帮助您为测试准备数据。
缺点：|2749800|-+a+lot+of+work+is+required+to+create+and+maintain+schema+and+data.+especially+when+your+project+is+in+a+intensive+development+stage.
-+it's+another+abstraction+layer+so+if+suddenly+you+want+to+use+some+db+feature+that+is+unsupported+by+this+tool,+it+may+be+difficult+to+test+it|code-block|syntax|javascript|2749801|​|2749802|检出+-旨在为您提供完整、可使用和可扩展的生命周期(公开:我是一个创建者)。
缺点：|2749803|-+free+only+for+small+projects
-+very+young+project|2749804|2749805|你也可以自己填补空白。和往常一样，这是一种交易:时间与金钱|2749806|entityMap|0|LINK|mutability|MUTABLE|url|https://www.testcontainers.org/|1|http://dbunit.sourceforge.net/|2|https://github.com/piotrturski/testegration^0|0|0|0|0|0|0|0|0|4|0|0|0|4|1|0|0|0|0|2|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1M|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1N|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|1O|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1P|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1Q|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1R|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1S|8|@]|9|@$R|1T|S|1U|1|1V]]|A|$]]|$1|T|3|U|5|Q|7|1W|8|@]|9|@$R|1X|S|1Y|1|1Z]]|A|$]]|$1|V|3|W|5|X|7|20|8|@]|9|@]|A|$Y|Z]]|$1|10|3|11|5|6|7|21|8|@]|9|@]|A|$]]|$1|12|3|13|5|Q|7|22|8|@]|9|@$R|23|S|24|1|25]]|A|$]]|$1|14|3|15|5|X|7|26|8|@]|9|@]|A|$Y|Z]]|$1|16|3|11|5|6|7|27|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|28|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|29|8|@]|9|@]|A|$]]]|1A|$1B|$5|1C|1D|1E|A|$1F|1G]]|1H|$5|1C|1D|1E|A|$1F|1I]]|1J|$5|1C|1D|1E|A|$1F|1K]]]]

You should NOT change your queries. In tests you should only change the connection url your application will use. The problem is, how to get that url working.

To have full test coverage you need the same db (as you noticed, h2 and other in-memory db are not very compatible). postgres doesn't have in-memory mode so you have to manage the lifecycle yourself. there is a few decisions you have to make. some of them:

<ul>
<li>where will you get the db from: require all the devs to provide postgres (installation / docker / vagrant) or automate the setup?</li>
<li>how to prepare db for tests: manual schema setup and cleanup?</li>
<li>how to reset db between tests: restart? always rollback? predefined and separately defined content? some kind of reverse operations?</li>
<li>if and how to make those tests fast?</li>
</ul>

there are some tools that can help you solve some of the problems:

<ol>
<li><a href="https://www.testcontainers.org/" rel="nofollow noreferrer">testcontainers</a> will help you provide 
db.</li>
<li><a href="http://dbunit.sourceforge.net/" rel="nofollow noreferrer">dbunit</a> - will help you prepare data for your test. 

cons: 

<ul>
<li>a lot of work is required to create and maintain schema and data. especially when your project is in a intensive development stage.</li>
<li>it's another abstraction layer so if suddenly you want to use some db feature that is unsupported by this tool, it may be difficult to test it</li>
</ul></li>
<li><a href="https://github.com/piotrturski/testegration" rel="nofollow noreferrer">testegration</a> - intents to provide you full, ready to use and extensible lifecycle (disclosure: i'm a creator). 

cons: 

<ul>
<li>free only for small projects</li>
<li>very young project</li>
</ul></li>
</ol>

you can also fill the gaps on your own. as always it's a trade: time vs money

There were some proposed solutions to the question "How to test SQL statements in an application" -

<ul>
<li>Using RAM memory - I can't change the configuration of staging environment where testing happens.</li>
<li>Using H2 - Not very compatible even in PostgreSQL mode</li>
<li>Use the same database to run the tests.</li>
<li>Using in-memory mode - PostgreSQL doesn't have one.</li>
</ul>

The third one was viable and I looked into <a href="https://www.testcontainers.org/" rel="nofollow noreferrer">Test Containers</a> which is actually a beautiful solution but a relatively new one. As a result, our company is sceptical of adopting it.

We use <code>Mybatis</code> to access <code>PostgreSQL</code>. 

Another way would be to recreate entire schema and populate required tables before tests. Here is the problem, I could create and delete schema with tables with the same name. To avoid name collision I'd have to change schema's name, as a result, even queries should be renamed which is not at all preferred. Is there a way to do this without changing queries but pointing them to the dummy schema.

How to use the actual database for integration testing?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

对于“如何在应用程序中测试SQL语句”这个问题，有一些建议的解决方案-使用RAM内存-我不能更改测试发生的暂存环境的配置。使用H2 -即使在PostgreSQL模式下也不是很兼容使用相同的数据库运行测试。使用内存中的模式- PostgreSQL没有一个.第三个方案是可行的，我研究了，它实际上是一个漂亮的解决方案，但相对...

问如何使用实际数据库进行集成测试？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用实际数据库进行集成测试？EN