|
|
|
|
|
<!DOCTYPE HTML>
|
|
|
|
|
|
<html lang="zh-CN" class="light" dir="ltr">
|
|
|
|
|
|
<head>
|
|
|
|
|
|
<!-- Book generated using mdBook -->
|
|
|
|
|
|
<meta charset="UTF-8">
|
|
|
|
|
|
<title>单元测试和集成测试 - Rust语言圣经(Rust Course)</title>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Custom HTML head -->
|
|
|
|
|
|
|
|
|
|
|
|
<meta name="description" content="">
|
|
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
|
|
|
|
<meta name="theme-color" content="#ffffff">
|
|
|
|
|
|
|
|
|
|
|
|
<link rel="icon" href="../favicon.svg">
|
|
|
|
|
|
<link rel="shortcut icon" href="../favicon.png">
|
|
|
|
|
|
<link rel="stylesheet" href="../css/variables.css">
|
|
|
|
|
|
<link rel="stylesheet" href="../css/general.css">
|
|
|
|
|
|
<link rel="stylesheet" href="../css/chrome.css">
|
|
|
|
|
|
<link rel="stylesheet" href="../css/print.css" media="print">
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Fonts -->
|
|
|
|
|
|
<link rel="stylesheet" href="../FontAwesome/css/font-awesome.css">
|
|
|
|
|
|
<link rel="stylesheet" href="../fonts/fonts.css">
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Highlight.js Stylesheets -->
|
|
|
|
|
|
<link rel="stylesheet" href="../highlight.css">
|
|
|
|
|
|
<link rel="stylesheet" href="../tomorrow-night.css">
|
|
|
|
|
|
<link rel="stylesheet" href="../ayu-highlight.css">
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Custom theme stylesheets -->
|
|
|
|
|
|
<link rel="stylesheet" href="../theme/style.css">
|
|
|
|
|
|
|
|
|
|
|
|
</head>
|
|
|
|
|
|
<body class="sidebar-visible no-js">
|
|
|
|
|
|
<div id="body-container">
|
|
|
|
|
|
<!-- Provide site root to javascript -->
|
|
|
|
|
|
<script>
|
|
|
|
|
|
var path_to_root = "../";
|
|
|
|
|
|
var default_theme = window.matchMedia("(prefers-color-scheme: dark)").matches ? "navy" : "light";
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Work around some values being stored in localStorage wrapped in quotes -->
|
|
|
|
|
|
<script>
|
|
|
|
|
|
try {
|
|
|
|
|
|
var theme = localStorage.getItem('mdbook-theme');
|
|
|
|
|
|
var sidebar = localStorage.getItem('mdbook-sidebar');
|
|
|
|
|
|
|
|
|
|
|
|
if (theme.startsWith('"') && theme.endsWith('"')) {
|
|
|
|
|
|
localStorage.setItem('mdbook-theme', theme.slice(1, theme.length - 1));
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
if (sidebar.startsWith('"') && sidebar.endsWith('"')) {
|
|
|
|
|
|
localStorage.setItem('mdbook-sidebar', sidebar.slice(1, sidebar.length - 1));
|
|
|
|
|
|
}
|
|
|
|
|
|
} catch (e) { }
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Set the theme before any content is loaded, prevents flash -->
|
|
|
|
|
|
<script>
|
|
|
|
|
|
var theme;
|
|
|
|
|
|
try { theme = localStorage.getItem('mdbook-theme'); } catch(e) { }
|
|
|
|
|
|
if (theme === null || theme === undefined) { theme = default_theme; }
|
|
|
|
|
|
var html = document.querySelector('html');
|
|
|
|
|
|
html.classList.remove('light')
|
|
|
|
|
|
html.classList.add(theme);
|
|
|
|
|
|
var body = document.querySelector('body');
|
|
|
|
|
|
body.classList.remove('no-js')
|
|
|
|
|
|
body.classList.add('js');
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<input type="checkbox" id="sidebar-toggle-anchor" class="hidden">
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Hide / unhide sidebar before it is displayed -->
|
|
|
|
|
|
<script>
|
|
|
|
|
|
var body = document.querySelector('body');
|
|
|
|
|
|
var sidebar = null;
|
|
|
|
|
|
var sidebar_toggle = document.getElementById("sidebar-toggle-anchor");
|
|
|
|
|
|
if (document.body.clientWidth >= 1080) {
|
|
|
|
|
|
try { sidebar = localStorage.getItem('mdbook-sidebar'); } catch(e) { }
|
|
|
|
|
|
sidebar = sidebar || 'visible';
|
|
|
|
|
|
} else {
|
|
|
|
|
|
sidebar = 'hidden';
|
|
|
|
|
|
}
|
|
|
|
|
|
sidebar_toggle.checked = sidebar === 'visible';
|
|
|
|
|
|
body.classList.remove('sidebar-visible');
|
|
|
|
|
|
body.classList.add("sidebar-" + sidebar);
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<nav id="sidebar" class="sidebar" aria-label="Table of contents">
|
|
|
|
|
|
<div class="sidebar-scrollbox">
|
|
|
|
|
|
<ol class="chapter"><li class="chapter-item affix "><a href="../about-book.html">关于本书</a></li><li class="chapter-item affix "><a href="../into-rust.html">进入 Rust 编程世界</a></li><li class="chapter-item affix "><a href="../first-try/sth-you-should-not-do.html">避免从入门到放弃</a></li><li class="chapter-item affix "><a href="../community.html">社区和锈书</a></li><li class="spacer"></li><li class="chapter-item affix "><a href="../some-thoughts.html">Datav: 可编程的数据可视化平台和可观测性平台</a></li><li class="chapter-item affix "><li class="part-title">Rust 语言基础学习</li><li class="spacer"></li><li class="chapter-item "><a href="../first-try/intro.html"><strong aria-hidden="true">1.</strong> 寻找牛刀，以便小试</a><a class="toggle"><div>❱</div></a></li><li><ol class="section"><li class="chapter-item "><a href="../first-try/installation.html"><strong aria-hidden="true">1.1.</strong> 安装 Rust 环境</a></li><li class="chapter-item "><a href="../first-try/editor.html"><strong aria-hidden="true">1.2.</strong> 墙推 VSCode!</a></li><li class="chapter-item "><a href="../first-try/cargo.html"><strong aria-hidden="true">1.3.</strong> 认识 Cargo</a></li><li class="chapter-item "><a href="../first-try/hello-world.html"><strong aria-hidden="true">1.4.</strong> 不仅仅是 Hello world</a></li><li class="chapter-item "><a href="../first-try/slowly-downloading.html"><strong aria-hidden="true">1.5.</strong> 下载依赖太慢了？</a></li></ol></li><li class="chapter-item "><a href="../basic/intro.html"><strong aria-hidden="true">2.</strong> Rust 基础入门</a><a class="toggle"><div>❱</div></a></li><li><ol class="section"><li class="chapter-item "><a href="../basic/variable.html"><strong aria-hidden="true">2.1.</strong> 变量绑定与解构</a></li><li class="chapter-item "><a href="../basic/base-type/index.html"><strong aria-hidden="true">2.2.</strong> 基本类型</a><a class="toggle"><div>❱</div></a></li><li><ol class="section"><li class="chapter-item "><a href="../basic/base-type/numbers.html"><strong aria-hidden="true">2.2.1.</strong> 数值类型</a></li><li class="chapter-item "><a href="../basic/base-type/char-bool.html"><strong aria-hidden="true">2.2.2.</strong> 字符、布尔、单元类型</a></li><li class="chapter-item "><a href="../basic/base-type/statement-expression.html"><strong aria-hidden="true">2.2.3.</strong> 语句与表达式</a></li><li class="chapter-item "><a href="../basic/base-type/function.html"><strong aria-hidden="true">2.2.4.</strong> 函数</a></li></ol></li><li class="chapter-item "><a href="../basic/ownership/index.html"><strong aria-hidden="true">2.3.</strong> 所有权和借用</a><a class="toggle"><div>❱</div></a></li><li><ol class="section"><li class="chapter-item "><a href="../basic/ownership/ownership.html"><strong aria-hidden="true">2.3.1.</strong> 所有权</a></li><li class="chapter-item "><a href="../basic/ownership/borrowing.html"><strong aria-hidden="true">2.3.2.</strong> 引用与借用</a></li></ol></li><li class="chapter-item "><a href="../basic/compound-type/intro.html"><strong aria-hidden="true">2.4.</strong> 复合类型</a><a class="toggle"><div>❱</div></a></li><li><ol class="section"><li class="chapter-item "><a href="../basic/compound-type/string-slice.html"><strong aria-hidden="true">2.4.1.</strong> 字符串与切片</a></li><li class="chapter-item "><a href="../basic/compound-type/tuple.html"><strong aria-hidden="true">2.4.2.</strong> 元组</a></li><li class="chapter-item "><a href="../basic/compound-type/struct.html"><strong aria-hidden="true">2.4.3.</strong> 结构体</a></li><li class="chapter-item "><a href="../basic/compound-type/enum.html"><strong aria-hidden="true">2.4.4.</strong> 枚举</a></li><li class="chapter-item "><a href="../basic/compound-type/array.html"><strong aria-hidden="true">2.4.5.</strong> 数组</a></li></ol></li><li class="chapter-item "><a href="../basic/flow-control.html"><strong aria-hidden="true">2.5.</strong> 流程控制</a></li><li class="cha
|
|
|
|
|
|
</div>
|
|
|
|
|
|
<div id="sidebar-resize-handle" class="sidebar-resize-handle">
|
|
|
|
|
|
<div class="sidebar-resize-indicator"></div>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</nav>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Track and set sidebar scroll position -->
|
|
|
|
|
|
<script>
|
|
|
|
|
|
var sidebarScrollbox = document.querySelector('#sidebar .sidebar-scrollbox');
|
|
|
|
|
|
sidebarScrollbox.addEventListener('click', function(e) {
|
|
|
|
|
|
if (e.target.tagName === 'A') {
|
|
|
|
|
|
sessionStorage.setItem('sidebar-scroll', sidebarScrollbox.scrollTop);
|
|
|
|
|
|
}
|
|
|
|
|
|
}, { passive: true });
|
|
|
|
|
|
var sidebarScrollTop = sessionStorage.getItem('sidebar-scroll');
|
|
|
|
|
|
sessionStorage.removeItem('sidebar-scroll');
|
|
|
|
|
|
if (sidebarScrollTop) {
|
|
|
|
|
|
// preserve sidebar scroll position when navigating via links within sidebar
|
|
|
|
|
|
sidebarScrollbox.scrollTop = sidebarScrollTop;
|
|
|
|
|
|
} else {
|
|
|
|
|
|
// scroll sidebar to current active section when navigating via "next/previous chapter" buttons
|
|
|
|
|
|
var activeSection = document.querySelector('#sidebar .active');
|
|
|
|
|
|
if (activeSection) {
|
|
|
|
|
|
activeSection.scrollIntoView({ block: 'center' });
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<div id="page-wrapper" class="page-wrapper">
|
|
|
|
|
|
|
|
|
|
|
|
<div class="page">
|
|
|
|
|
|
<div id="menu-bar-hover-placeholder"></div>
|
|
|
|
|
|
<div id="menu-bar" class="menu-bar sticky">
|
|
|
|
|
|
<div class="left-buttons">
|
|
|
|
|
|
<label id="sidebar-toggle" class="icon-button" for="sidebar-toggle-anchor" title="Toggle Table of Contents" aria-label="Toggle Table of Contents" aria-controls="sidebar">
|
|
|
|
|
|
<i class="fa fa-bars"></i>
|
|
|
|
|
|
</label>
|
|
|
|
|
|
<button id="theme-toggle" class="icon-button" type="button" title="Change theme" aria-label="Change theme" aria-haspopup="true" aria-expanded="false" aria-controls="theme-list">
|
|
|
|
|
|
<i class="fa fa-paint-brush"></i>
|
|
|
|
|
|
</button>
|
|
|
|
|
|
<ul id="theme-list" class="theme-popup" aria-label="Themes" role="menu">
|
|
|
|
|
|
<li role="none"><button role="menuitem" class="theme" id="light">Light</button></li>
|
|
|
|
|
|
<li role="none"><button role="menuitem" class="theme" id="rust">Rust</button></li>
|
|
|
|
|
|
<li role="none"><button role="menuitem" class="theme" id="coal">Coal</button></li>
|
|
|
|
|
|
<li role="none"><button role="menuitem" class="theme" id="navy">Navy</button></li>
|
|
|
|
|
|
<li role="none"><button role="menuitem" class="theme" id="ayu">Ayu</button></li>
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
<button id="search-toggle" class="icon-button" type="button" title="Search. (Shortkey: s)" aria-label="Toggle Searchbar" aria-expanded="false" aria-keyshortcuts="S" aria-controls="searchbar">
|
|
|
|
|
|
<i class="fa fa-search"></i>
|
|
|
|
|
|
</button>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<h1 class="menu-title">Rust语言圣经(Rust Course)</h1>
|
|
|
|
|
|
|
|
|
|
|
|
<div class="right-buttons">
|
|
|
|
|
|
<a href="../print.html" title="Print this book" aria-label="Print this book">
|
|
|
|
|
|
<i id="print-button" class="fa fa-print"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
<a href="https://github.com/sunface/rust-course" title="Git repository" aria-label="Git repository">
|
|
|
|
|
|
<i id="git-repository-button" class="fa fa-github"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
<a href="https://github.com/sunface/rust-course/edit/main/src/test/unit-integration-test.md" title="Suggest an edit" aria-label="Suggest an edit">
|
|
|
|
|
|
<i id="git-edit-button" class="fa fa-edit"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<div id="search-wrapper" class="hidden">
|
|
|
|
|
|
<form id="searchbar-outer" class="searchbar-outer">
|
|
|
|
|
|
<input type="search" id="searchbar" name="searchbar" placeholder="Search this book ..." aria-controls="searchresults-outer" aria-describedby="searchresults-header">
|
|
|
|
|
|
</form>
|
|
|
|
|
|
<div id="searchresults-outer" class="searchresults-outer hidden">
|
|
|
|
|
|
<div id="searchresults-header" class="searchresults-header"></div>
|
|
|
|
|
|
<ul id="searchresults">
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Apply ARIA attributes after the sidebar and the sidebar toggle button are added to the DOM -->
|
|
|
|
|
|
<script>
|
|
|
|
|
|
document.getElementById('sidebar-toggle').setAttribute('aria-expanded', sidebar === 'visible');
|
|
|
|
|
|
document.getElementById('sidebar').setAttribute('aria-hidden', sidebar !== 'visible');
|
|
|
|
|
|
Array.from(document.querySelectorAll('#sidebar a')).forEach(function(link) {
|
|
|
|
|
|
link.setAttribute('tabIndex', sidebar === 'visible' ? 0 : -1);
|
|
|
|
|
|
});
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<div id="content" class="content">
|
|
|
|
|
|
<!-- Page table of contents -->
|
|
|
|
|
|
<div class="sidetoc"><nav class="pagetoc"></nav></div>
|
|
|
|
|
|
<main>
|
|
|
|
|
|
<h1 id="单元测试集成测试"><a class="header" href="#单元测试集成测试">单元测试、集成测试</a></h1>
|
|
|
|
|
|
<p>在了解了如何在 Rust 中写测试用例后，本章节我们将学习如何实现单元测试、集成测试，其实它们用到的技术还是<a href="https://course.rs/test/write-tests.html">上一章节</a>中的测试技术，只不过对如何组织测试代码提出了新的要求。</p>
|
|
|
|
|
|
<h2 id="单元测试"><a class="header" href="#单元测试">单元测试</a></h2>
|
|
|
|
|
|
<p>单元测试目标是测试某一个代码单元(一般都是函数)，验证该单元是否能按照预期进行工作，例如测试一个 <code>add</code> 函数，验证当给予两个输入时，最终返回的和是否符合预期。</p>
|
|
|
|
|
|
<p>在 Rust 中，单元测试的惯例是将测试代码的模块跟待测试的正常代码放入同一个文件中，例如 <code>src/lib.rs</code> 文件中有如下代码:</p>
|
|
|
|
|
|
<pre><pre class="playground"><code class="language-rust edition2021"><span class="boring">#![allow(unused)]
|
|
|
|
|
|
</span><span class="boring">fn main() {
|
|
|
|
|
|
</span>pub fn add_two(a: i32) -> i32 {
|
|
|
|
|
|
a + 2
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
#[cfg(test)]
|
|
|
|
|
|
mod tests {
|
|
|
|
|
|
use super::*;
|
|
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
|
fn it_works() {
|
|
|
|
|
|
assert_eq!(add_two(2), 4);
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
<span class="boring">}</span></code></pre></pre>
|
|
|
|
|
|
<p><code>add_two</code> 是我们的项目代码，为了对它进行测试，我们在同一个文件中编写了测试模块 <code>tests</code>，并使用 <code>#[cfg(test)]</code> 进行了标注。</p>
|
|
|
|
|
|
<h4 id="条件编译-cfgtest"><a class="header" href="#条件编译-cfgtest">条件编译 <code>#[cfg(test)]</code></a></h4>
|
|
|
|
|
|
<p>上面代码中的 <code>#[cfg(test)]</code> 标注可以告诉 Rust 只有在 <code>cargo test</code> 时才编译和运行模块 <code>tests</code>，其它时候当这段代码是空气即可，例如在 <code>cargo build</code> 时。这么做有几个好处：</p>
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
<li>节省构建代码时的编译时间</li>
|
|
|
|
|
|
<li>减小编译出的可执行文件的体积</li>
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
<p>其实集成测试就不需要这个标注，因为它们被放入单独的目录文件中，而单元测试是跟正常的逻辑代码在同一个文件，因此必须对其进行特殊的标注，以便 Rust 可以识别。</p>
|
|
|
|
|
|
<p>在 <code>#[cfg(test)]</code> 中，<code>cfg</code> 是配置 <code>configuration</code> 的缩写，它告诉 Rust ：当 <code>test</code> 配置项存在时，才运行下面的代码，而 <code>cargo test</code> 在运行时，就会将 <code>test</code> 这个配置项传入进来，因此后面的 <code>tests</code> 模块会被包含进来。</p>
|
|
|
|
|
|
<p>大家看出来了吗？这是典型的条件编译，<code>Cargo</code> 会根据指定的配置来选择是否编译指定的代码，事实上关于条件编译 Rust 能做的不仅仅是这些，在 <a href="https://course.rs/cargo/intro.html"><code>Cargo</code> 专题</a>中我们会进行更为详细的介绍。</p>
|
|
|
|
|
|
<h4 id="测试私有函数"><a class="header" href="#测试私有函数">测试私有函数</a></h4>
|
|
|
|
|
|
<p>关于私有函数能否被直接测试，编程社区里一直争论不休，甚至于部分语言可能都不支持对私有函数进行测试或者难以测试。无论你的立场如何，反正 Rust 是支持对私有函数进行测试的:</p>
|
|
|
|
|
|
<pre><pre class="playground"><code class="language-rust edition2021"><span class="boring">#![allow(unused)]
|
|
|
|
|
|
</span><span class="boring">fn main() {
|
|
|
|
|
|
</span>pub fn add_two(a: i32) -> i32 {
|
|
|
|
|
|
internal_adder(a, 2)
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
fn internal_adder(a: i32, b: i32) -> i32 {
|
|
|
|
|
|
a + b
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
#[cfg(test)]
|
|
|
|
|
|
mod tests {
|
|
|
|
|
|
use super::*;
|
|
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
|
fn internal() {
|
|
|
|
|
|
assert_eq!(4, internal_adder(2, 2));
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
<span class="boring">}</span></code></pre></pre>
|
|
|
|
|
|
<p><code>internal_adder</code> 并没有使用 <code>pub</code> 进行声明，因此它是一个私有函数。根据我们之前<a href="">学过的内容</a>，<code>tests</code> 作为另一个模块，是绝对无法对它进行调用的，因为它们根本不在同一个模块中！</p>
|
|
|
|
|
|
<p>但是在上述代码中，我们使用 <code>use super::*;</code> 将 <code>tests</code> 的父模块中的所有内容引入到当前作用域中，这样就可以非常简单的实现对私有函数的测试。</p>
|
|
|
|
|
|
<h2 id="集成测试"><a class="header" href="#集成测试">集成测试</a></h2>
|
|
|
|
|
|
<p>与单元测试的同吃同住不同，集成测试的代码是在一个单独的目录下的。由于它们使用跟其它模块一样的方式去调用你想要测试的代码，因此只能调用通过 <code>pub</code> 定义的 <code>API</code>，这一点与单元测试有很大的不同。</p>
|
|
|
|
|
|
<p>如果说单元测试是对代码单元进行测试，那集成测试则是对某一个功能或者接口进行测试，因此单元测试的通过，并不意味着集成测试就能通过：局部上反映不出的问题，在全局上很可能会暴露出来。</p>
|
|
|
|
|
|
<h4 id="tests-目录"><a class="header" href="#tests-目录"><em>tests</em> 目录</a></h4>
|
|
|
|
|
|
<p>一个标准的 Rust 项目，在它的根目录下会有一个 <code>tests</code> 目录，大名鼎鼎的 <a href="https://github.com/BurntSushi/ripgrep"><code>ripgrep</code></a> 也不能免俗。</p>
|
|
|
|
|
|
<p>没错，该目录就是用来存放集成测试的，Cargo 会自动来此目录下寻找集成测试文件。我们可以在该目录下创建任何文件，Cargo 会对每个文件都进行自动编译，但友情提示下，最好按照合适的逻辑来组织你的测试代码。</p>
|
|
|
|
|
|
<p>首先来创建一个集成测试文件 <code>tests/integration_test.rs</code> ，注意，<code>tests</code> 目录一般来说需要手动创建，该目录在项目的根目录下，跟 <code>src</code> 目录同级。然后在文件中填入如下测试代码：</p>
|
|
|
|
|
|
<pre><pre class="playground"><code class="language-rust edition2021"><span class="boring">#![allow(unused)]
|
|
|
|
|
|
</span><span class="boring">fn main() {
|
|
|
|
|
|
</span>use adder;
|
|
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
|
fn it_adds_two() {
|
|
|
|
|
|
assert_eq!(4, adder::add_two(2));
|
|
|
|
|
|
}
|
|
|
|
|
|
<span class="boring">}</span></code></pre></pre>
|
|
|
|
|
|
<p>这段测试代码是对之前<strong>私有函数</strong>中的示例进行测试，该示例代码在 <code>src/lib.rs</code> 中。</p>
|
|
|
|
|
|
<p>首先与单元测试有所不同，我们并没有创建测试模块。其次，<code>tests</code> 目录下的每个文件都是一个单独的包，我们需要将待测试的包引入到当前包的作用域后: <code>use adder</code>，才能进行测试 。大家应该还记得<a href="https://course.rs/advance/crate-module/crate.html">包和模块章节</a>中讲过的内容吧？在创建项目后，<code>src/lib.rs</code> 自动创建一个与项目同名的 <code>lib</code> 类型的包，由于我们的项目名是 <code>adder</code>，因此包名也是 <code>adder</code>。</p>
|
|
|
|
|
|
<p>因为 <code>tests</code> 目录本身就说明了它的特殊用途，因此我们无需再使用 <code>#[cfg(test)]</code> 来取悦 Cargo。后者会在运行 <code>cargo test</code> 时，对 <code>tests</code> 目录中的每个文件都进行编译运行。</p>
|
|
|
|
|
|
<pre><code class="language-shell">$ cargo test
|
|
|
|
|
|
Running unittests (target/debug/deps/adder-8a400aa2b5212836)
|
|
|
|
|
|
|
|
|
|
|
|
running 1 test
|
|
|
|
|
|
test tests::it_works ... ok
|
|
|
|
|
|
|
|
|
|
|
|
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
|
|
|
|
|
|
Running tests/integration_test.rs (target/debug/deps/integration_test-2d3aeee6f15d1f20)
|
|
|
|
|
|
|
|
|
|
|
|
running 1 test
|
|
|
|
|
|
test it_adds_two ... ok
|
|
|
|
|
|
|
|
|
|
|
|
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
|
|
|
|
|
|
Doc-tests adder
|
|
|
|
|
|
|
|
|
|
|
|
running 0 tests
|
|
|
|
|
|
|
|
|
|
|
|
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>运行 <code>cargo test</code> ，可以看到上述输出。测试内容有三个部分：单元测试，集成测试和文档测试。</p>
|
|
|
|
|
|
<p>首先是单元测试被运行 <code>Running unittests</code> ，其次就是我们的主角集成测试的运行 <code>Running tests/integration_test.rs</code>，可以看出，集成测试的输出内容与单元测试并没有大的区别。最后运行的是文档测试 <code>Doc-tests adder</code>。</p>
|
|
|
|
|
|
<p>与单元测试类似，我们可以通过<a href="https://course.rs/test/write-tests.html#%E6%8C%87%E5%AE%9A%E8%BF%90%E8%A1%8C%E4%B8%80%E9%83%A8%E5%88%86%E6%B5%8B%E8%AF%95">指定名称的方式</a>来运行特定的集成测试用例:</p>
|
|
|
|
|
|
<pre><code class="language-shell">$ cargo test --test integration_test
|
|
|
|
|
|
Running tests/integration_test.rs (target/debug/deps/integration_test-82e7799c1bc62298)
|
|
|
|
|
|
|
|
|
|
|
|
running 1 test
|
|
|
|
|
|
test it_adds_two ... ok
|
|
|
|
|
|
|
|
|
|
|
|
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>这次，单元测试、文档测试啥的都没有运行，只有集成测试目录下的 <code>integration_test</code> 文件被顺利执行。</p>
|
|
|
|
|
|
<p>大家可以尝试下在同一个测试文件中添加更多的测试用例或者添加更多的测试文件，并观察测试输出会如何变化。</p>
|
|
|
|
|
|
<h4 id="共享模块"><a class="header" href="#共享模块">共享模块</a></h4>
|
|
|
|
|
|
<p>在集成测试的 <code>tests</code> 目录下，每一个文件都是一个独立的包，这种组织方式可以很好的帮助我们理清测试代码的关系，但是如果大家想要在多个文件中共享同一个功能该怎么做？例如函数 <code>setup</code> 可以用于状态初始化，然后多个测试包都需要使用该函数进行状态的初始化。</p>
|
|
|
|
|
|
<p>也许你会想要创建一个 <code>tests/common.rs</code> 文件，然后将 <code>setup</code> 函数放入其中：</p>
|
|
|
|
|
|
<pre><pre class="playground"><code class="language-rust edition2021"><span class="boring">#![allow(unused)]
|
|
|
|
|
|
</span><span class="boring">fn main() {
|
|
|
|
|
|
</span>pub fn setup() {
|
|
|
|
|
|
// 初始化一些测试状态
|
|
|
|
|
|
// ...
|
|
|
|
|
|
}
|
|
|
|
|
|
<span class="boring">}</span></code></pre></pre>
|
|
|
|
|
|
<p>但是当我们运行 <code>cargo test</code> 后，会发现该函数被当作集成测试函数运行了，即使它并没有包含任何测试功能，也没有被其它测试文件所调用:</p>
|
|
|
|
|
|
<pre><code class="language-shell">$ cargo test
|
|
|
|
|
|
Running tests/common.rs (target/debug/deps/common-5c21f4f2c87696fb)
|
|
|
|
|
|
|
|
|
|
|
|
running 0 tests
|
|
|
|
|
|
|
|
|
|
|
|
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>显然，这个结果并不是我们想要的。<strong>为了避免这种输出，我们不能创建 <code>tests/common.rs</code>，而是要创建 <code>tests/common/mod.rs</code>。</strong>，此时再运行 <code>cargo test</code> 就不会再看到相应的输出。 原因是<strong>通过这种文件组织和命名方式， Rust 不再将 <code>common</code> 模块看作是集成测试文件。</strong></p>
|
|
|
|
|
|
<p>总结来说，<strong><code>tests</code> 目录下的子目录中的文件不会被当作独立的包，也不会有测试输出</strong>。</p>
|
|
|
|
|
|
<pre><pre class="playground"><code class="language-rust edition2021"><span class="boring">#![allow(unused)]
|
|
|
|
|
|
</span><span class="boring">fn main() {
|
|
|
|
|
|
</span>use adder;
|
|
|
|
|
|
|
|
|
|
|
|
mod common;
|
|
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
|
fn it_adds_two() {
|
|
|
|
|
|
common::setup();
|
|
|
|
|
|
assert_eq!(4, adder::add_two(2));
|
|
|
|
|
|
}
|
|
|
|
|
|
<span class="boring">}</span></code></pre></pre>
|
|
|
|
|
|
<p>此时，就可以在测试中调用 <code>common</code> 中的共享函数了，不过还有一点值得注意，为了使用 <code>common</code>，这里使用了 <code>mod common</code> 的方式来声明该模块。</p>
|
|
|
|
|
|
<h4 id="二进制包的集成测试"><a class="header" href="#二进制包的集成测试">二进制包的集成测试</a></h4>
|
|
|
|
|
|
<p>目前来说，Rust 只支持对 <code>lib</code> 类型的包进行集成测试，对于二进制包例如 <code>src/main.rs</code> 是无能为力的。原因在于，我们无法在其它包中使用 <code>use</code> 引入二进制包，而只有 <code>lib</code> 类型的包才能被引入，例如 <code>src/lib.rs</code>。</p>
|
|
|
|
|
|
<p>这就是为何我们需要将代码逻辑从 <code>src/main.rs</code> 剥离出去放入 <code>lib</code> 包中，例如很多 Rust 项目中都同时有 <code>src/main.rs</code> 和 <code>src/lib.rs</code> ，前者中只保留代码的主体脉络部分，而具体的实现通通放在类似后者的 <code>lib</code> 包中。</p>
|
|
|
|
|
|
<p>这样，我们就可以对 <code>lib</code> 包中的具体实现进行集成测试，由于 <code>main.rs</code> 中的主体脉络足够简单，当集成测试通过时，意味着 <code>main.rs</code> 中相应的调用代码也将正常运行。</p>
|
|
|
|
|
|
<h2 id="总结"><a class="header" href="#总结">总结</a></h2>
|
|
|
|
|
|
<p>Rust 提供了单元测试和集成测试两种方式来帮助我们组织测试代码以解决代码正确性问题。</p>
|
|
|
|
|
|
<p>单元测试针对的是具体的代码单元，例如函数，而集成测试往往针对的是一个功能或接口 API，正因为目标上的不同，导致了两者在组织方式上的不同：</p>
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
<li>单元测试的模块和待测试的代码在同一个文件中，且可以很方便地对私有函数进行测试</li>
|
|
|
|
|
|
<li>集成测试文件放在项目根目录下的 <code>tests</code> 目录中，由于该目录下每个文件都是一个包，我们必须要引入待测试的代码到当前包的作用域中，才能进行测试，正因为此，集成测试只能对声明为 <code>pub</code> 的 API 进行测试</li>
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
<p>下个章节，我们再来看看该如何使用 <code>GitHub Actions</code> 对 Rust 项目进行持续集成。</p>
|
|
|
|
|
|
|
|
|
|
|
|
<div id="giscus-container"></div>
|
|
|
|
|
|
</main>
|
|
|
|
|
|
|
|
|
|
|
|
<nav class="nav-wrapper" aria-label="Page navigation">
|
|
|
|
|
|
<!-- Mobile navigation buttons -->
|
|
|
|
|
|
<a rel="prev" href="../test/write-tests.html" class="mobile-nav-chapters previous" title="Previous chapter" aria-label="Previous chapter" aria-keyshortcuts="Left">
|
|
|
|
|
|
<i class="fa fa-angle-left"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
|
|
|
|
|
|
<a rel="next prefetch" href="../test/assertion.html" class="mobile-nav-chapters next" title="Next chapter" aria-label="Next chapter" aria-keyshortcuts="Right">
|
|
|
|
|
|
<i class="fa fa-angle-right"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
|
|
|
|
|
|
<div style="clear: both"></div>
|
|
|
|
|
|
</nav>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<nav class="nav-wide-wrapper" aria-label="Page navigation">
|
|
|
|
|
|
<a rel="prev" href="../test/write-tests.html" class="nav-chapters previous" title="Previous chapter" aria-label="Previous chapter" aria-keyshortcuts="Left">
|
|
|
|
|
|
<i class="fa fa-angle-left"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
|
|
|
|
|
|
<a rel="next prefetch" href="../test/assertion.html" class="nav-chapters next" title="Next chapter" aria-label="Next chapter" aria-keyshortcuts="Right">
|
|
|
|
|
|
<i class="fa fa-angle-right"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
</nav>
|
|
|
|
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<script>
|
|
|
|
|
|
window.playground_copyable = true;
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<script src="../ace.js"></script>
|
|
|
|
|
|
<script src="../editor.js"></script>
|
|
|
|
|
|
<script src="../mode-rust.js"></script>
|
|
|
|
|
|
<script src="../theme-dawn.js"></script>
|
|
|
|
|
|
<script src="../theme-tomorrow_night.js"></script>
|
|
|
|
|
|
|
|
|
|
|
|
<script src="../elasticlunr.min.js"></script>
|
|
|
|
|
|
<script src="../mark.min.js"></script>
|
|
|
|
|
|
<script src="../searcher.js"></script>
|
|
|
|
|
|
|
|
|
|
|
|
<script src="../clipboard.min.js"></script>
|
|
|
|
|
|
<script src="../highlight.js"></script>
|
|
|
|
|
|
<script src="../book.js"></script>
|
|
|
|
|
|
|
|
|
|
|
|
<script type="text/javascript" charset="utf-8">
|
|
|
|
|
|
var pagePath = "test/unit-integration-test.md"
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Custom JS scripts -->
|
|
|
|
|
|
<script src="../assets/custom.js"></script>
|
|
|
|
|
|
<script src="../assets/bigPicture.js"></script>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</body>
|
|
|
|
|
|
</html>
|
