mirror of
https://github.com/KaiserY/trpl-zh-cn
synced 2024-11-09 08:51:18 +08:00
493 lines
42 KiB
HTML
493 lines
42 KiB
HTML
|
<!DOCTYPE HTML>
|
|||
|
|
<html lang="en" class="light" dir="ltr">
|
|||
|
|
<head>
|
|||
|
|
<!-- Book generated using mdBook -->
|
|||
|
|
<meta charset="UTF-8">
|
|||
|
|
<title>控制测试如何运行 - Rust 程序设计语言 简体中文版</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="ferris.css">
|
|||
|
|
<link rel="stylesheet" href="theme/2018-edition.css">
|
|||
|
|
<link rel="stylesheet" href="theme/semantic-notes.css">
|
|||
|
|
<link rel="stylesheet" href="theme/listing.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 expanded affix "><a href="title-page.html">Rust 程序设计语言</a></li><li class="chapter-item expanded affix "><a href="foreword.html">前言</a></li><li class="chapter-item expanded affix "><a href="ch00-00-introduction.html">简介</a></li><li class="chapter-item expanded "><a href="ch01-00-getting-started.html"><strong aria-hidden="true">1.</strong> 入门指南</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch01-01-installation.html"><strong aria-hidden="true">1.1.</strong> 安装</a></li><li class="chapter-item expanded "><a href="ch01-02-hello-world.html"><strong aria-hidden="true">1.2.</strong> Hello, World!</a></li><li class="chapter-item expanded "><a href="ch01-03-hello-cargo.html"><strong aria-hidden="true">1.3.</strong> Hello, Cargo!</a></li></ol></li><li class="chapter-item expanded "><a href="ch02-00-guessing-game-tutorial.html"><strong aria-hidden="true">2.</strong> 写个猜数字游戏</a></li><li class="chapter-item expanded "><a href="ch03-00-common-programming-concepts.html"><strong aria-hidden="true">3.</strong> 常见编程概念</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch03-01-variables-and-mutability.html"><strong aria-hidden="true">3.1.</strong> 变量与可变性</a></li><li class="chapter-item expanded "><a href="ch03-02-data-types.html"><strong aria-hidden="true">3.2.</strong> 数据类型</a></li><li class="chapter-item expanded "><a href="ch03-03-how-functions-work.html"><strong aria-hidden="true">3.3.</strong> 函数</a></li><li class="chapter-item expanded "><a href="ch03-04-comments.html"><strong aria-hidden="true">3.4.</strong> 注释</a></li><li class="chapter-item expanded "><a href="ch03-05-control-flow.html"><strong aria-hidden="true">3.5.</strong> 控制流</a></li></ol></li><li class="chapter-item expanded "><a href="ch04-00-understanding-ownership.html"><strong aria-hidden="true">4.</strong> 认识所有权</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch04-01-what-is-ownership.html"><strong aria-hidden="true">4.1.</strong> 什么是所有权？</a></li><li class="chapter-item expanded "><a href="ch04-02-references-and-borrowing.html"><strong aria-hidden="true">4.2.</strong> 引用与借用</a></li><li class="chapter-item expanded "><a href="ch04-03-slices.html"><strong aria-hidden="true">4.3.</strong> Slice 类型</a></li></ol></li><li class="chapter-item expanded "><a href="ch05-00-structs.html"><strong aria-hidden="true">5.</strong> 使用结构体组织相关联的数据</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch05-01-defining-structs.html"><strong aria-hidden="true">5.1.</strong> 结构体的定义和实例化</a></li><li class="chapter-item expanded "><a href="ch05-02-example-structs.html"><strong aria-hidden="true">5.2.</strong> 结构体示例程序</a></li><li class="chapter-item expanded "><a href="ch05-03-method-syntax.html"><strong aria-hidden="true">5.3.</strong> 方法语法</a></li></ol></li><li class="chapter-item expanded "><a href="ch06-00-enums.html"><strong aria-hidden="true">6.</strong> 枚举和模式匹配</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch06-01-defining-an-enum.html"><strong aria-hidden="true">6.1.</strong> 枚举的定义</a></li><li class="chapter-item expanded "><a href="ch06-02-match.html"><strong aria-hidden="true">6.2.</strong> match 控制流结构</a></li><li class="chapter-item expanded "><a href="ch06-03-if-let.html"><strong aria-hidden="true">6.3.</strong> if let 简洁控制流</a></li></ol></li><li class="chapter-item expanded "><a href="ch07-00-managing-growing-projects-with-packages-crates-and-modules.html"><strong aria-hidden="true">7.</strong> 使用包、Crate 和模块管理不断增长的项目</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch07-01-packages-and-crates.html"><strong aria-hidden="true">7.1.</strong> 包和 Crate</a></li><li class="chapter-item expanded "><a h
|
|||
|
|
</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 程序设计语言 简体中文版</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/KaiserY/trpl-zh-cn/tree/main" title="Git repository" aria-label="Git repository">
|
|||
|
|
<i id="git-repository-button" class="fa fa-github"></i>
|
|||
|
|
</a>
|
|||
|
|
<a href="https://github.com/KaiserY/trpl-zh-cn/edit/main/src/ch11-02-running-tests.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">
|
|||
|
|
<main>
|
|||
|
|
<h2 id="控制测试如何运行"><a class="header" href="#控制测试如何运行">控制测试如何运行</a></h2>
|
|||
|
|
<blockquote>
|
|||
|
|
<p><a href="https://github.com/rust-lang/book/blob/main/src/ch11-02-running-tests.md">ch11-02-running-tests.md</a>
|
|||
|
|
<br>
|
|||
|
|
commit 34314c10f699cc882d4e0b06f2a24bd37a5435f2</p>
|
|||
|
|
</blockquote>
|
|||
|
|
<p>就像 <code>cargo run</code> 会编译代码并运行生成的二进制文件一样，<code>cargo test</code> 在测试模式下编译代码并运行生成的测试二进制文件。<code>cargo test</code> 产生的二进制文件的默认行为是并发运行所有的测试，并截获测试运行过程中产生的输出，阻止它们被显示出来，使得阅读测试结果相关的内容变得更容易。不过可以指定命令行参数来改变 <code>cargo test</code> 的默认行为。</p>
|
|||
|
|
<p>可以将一部分命令行参数传递给 <code>cargo test</code>，而将另外一部分传递给生成的测试二进制文件。为了分隔这两种参数，需要先列出传递给 <code>cargo test</code> 的参数，接着是分隔符 <code>--</code>，再之后是传递给测试二进制文件的参数。运行 <code>cargo test --help</code> 会提示 <code>cargo test</code> 的有关参数，而运行 <code>cargo test -- --help</code> 可以提示在分隔符之后使用的有关参数。</p>
|
|||
|
|
<h3 id="并行或连续的运行测试"><a class="header" href="#并行或连续的运行测试">并行或连续的运行测试</a></h3>
|
|||
|
|
<p>当运行多个测试时，Rust 默认使用线程来并行运行。这意味着测试会更快地运行完毕，所以你可以更快的得到代码能否工作的反馈。因为测试是在同时运行的，你应该确保测试不能相互依赖，或依赖任何共享的状态，包括依赖共享的环境，比如当前工作目录或者环境变量。</p>
|
|||
|
|
<p>举个例子，每一个测试都运行一些代码，假设这些代码都在硬盘上创建一个 <em>test-output.txt</em> 文件并写入一些数据。接着每一个测试都读取文件中的数据并断言这个文件包含特定的值，而这个值在每个测试中都是不同的。因为所有测试都是同时运行的，一个测试可能会在另一个测试读写文件过程中修改了文件。那么第二个测试就会失败，并不是因为代码不正确，而是因为测试并行运行时相互干扰。一个解决方案是使每一个测试读写不同的文件；另一个解决方案是一次运行一个测试。</p>
|
|||
|
|
<p>如果你不希望测试并行运行，或者想要更加精确的控制线程的数量，可以传递 <code>--test-threads</code> 参数和希望使用线程的数量给测试二进制文件。例如：</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test -- --test-threads=1
|
|||
|
|
</code></pre>
|
|||
|
|
<p>这里将测试线程设置为 <code>1</code>，告诉程序不要使用任何并行机制。这也会比并行运行花费更多时间，不过在有共享的状态时，测试就不会潜在的相互干扰了。</p>
|
|||
|
|
<h3 id="显示函数输出"><a class="header" href="#显示函数输出">显示函数输出</a></h3>
|
|||
|
|
<p>默认情况下，当测试通过时，Rust 的测试库会截获打印到标准输出的所有内容。比如在测试中调用了 <code>println!</code> 而测试通过了，我们将不会在终端看到 <code>println!</code> 的输出：只会看到说明测试通过的提示行。如果测试失败了，则会看到所有标准输出和其他错误信息。</p>
|
|||
|
|
<p>例如，示例 11-10 有一个无意义的函数，它打印出其参数的值并接着返回 10。接着还有一个会通过的测试和一个会失败的测试：</p>
|
|||
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|||
|
|
<pre><code class="language-rust panics noplayground">fn prints_and_returns_10(a: i32) -> i32 {
|
|||
|
|
println!("I got the value {a}");
|
|||
|
|
10
|
|||
|
|
}
|
|||
|
|
|
|||
|
|
#[cfg(test)]
|
|||
|
|
mod tests {
|
|||
|
|
use super::*;
|
|||
|
|
|
|||
|
|
#[test]
|
|||
|
|
fn this_test_will_pass() {
|
|||
|
|
let value = prints_and_returns_10(4);
|
|||
|
|
assert_eq!(value, 10);
|
|||
|
|
}
|
|||
|
|
|
|||
|
|
#[test]
|
|||
|
|
fn this_test_will_fail() {
|
|||
|
|
let value = prints_and_returns_10(8);
|
|||
|
|
assert_eq!(value, 5);
|
|||
|
|
}
|
|||
|
|
}</code></pre>
|
|||
|
|
<p><span class="caption">示例 11-10：一个调用了 <code>println!</code> 的函数的测试</span></p>
|
|||
|
|
<p>运行 <code>cargo test</code> 将会看到这些测试的输出：</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test
|
|||
|
|
Compiling silly-function v0.1.0 (file:///projects/silly-function)
|
|||
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.58s
|
|||
|
|
Running unittests src/lib.rs (target/debug/deps/silly_function-160869f38cff9166)
|
|||
|
|
|
|||
|
|
running 2 tests
|
|||
|
|
test tests::this_test_will_fail ... FAILED
|
|||
|
|
test tests::this_test_will_pass ... ok
|
|||
|
|
|
|||
|
|
failures:
|
|||
|
|
|
|||
|
|
---- tests::this_test_will_fail stdout ----
|
|||
|
|
I got the value 8
|
|||
|
|
thread 'tests::this_test_will_fail' panicked at src/lib.rs:19:9:
|
|||
|
|
assertion `left == right` failed
|
|||
|
|
left: 10
|
|||
|
|
right: 5
|
|||
|
|
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
|
|||
|
|
|
|||
|
|
|
|||
|
|
failures:
|
|||
|
|
tests::this_test_will_fail
|
|||
|
|
|
|||
|
|
test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|||
|
|
|
|||
|
|
error: test failed, to rerun pass `--lib`
|
|||
|
|
</code></pre>
|
|||
|
|
<p>注意输出中不会出现测试通过时打印的内容，即 <code>I got the value 4</code>。因为当测试通过时，这些输出会被截获。失败测试的输出 <code>I got the value 8</code> ，则出现在输出的测试摘要部分，同时也显示了测试失败的原因。</p>
|
|||
|
|
<p>如果你希望也能看到通过的测试中打印的值，也可以在结尾加上 <code>--show-output</code> 告诉 Rust 显示成功测试的输出。</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test -- --show-output
|
|||
|
|
</code></pre>
|
|||
|
|
<p>使用 <code>--show-output</code> 参数再次运行示例 11-10 中的测试会显示如下输出：</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test -- --show-output
|
|||
|
|
Compiling silly-function v0.1.0 (file:///projects/silly-function)
|
|||
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.60s
|
|||
|
|
Running unittests src/lib.rs (target/debug/deps/silly_function-160869f38cff9166)
|
|||
|
|
|
|||
|
|
running 2 tests
|
|||
|
|
test tests::this_test_will_fail ... FAILED
|
|||
|
|
test tests::this_test_will_pass ... ok
|
|||
|
|
|
|||
|
|
successes:
|
|||
|
|
|
|||
|
|
---- tests::this_test_will_pass stdout ----
|
|||
|
|
I got the value 4
|
|||
|
|
|
|||
|
|
|
|||
|
|
successes:
|
|||
|
|
tests::this_test_will_pass
|
|||
|
|
|
|||
|
|
failures:
|
|||
|
|
|
|||
|
|
---- tests::this_test_will_fail stdout ----
|
|||
|
|
I got the value 8
|
|||
|
|
thread 'tests::this_test_will_fail' panicked at src/lib.rs:19:9:
|
|||
|
|
assertion `left == right` failed
|
|||
|
|
left: 10
|
|||
|
|
right: 5
|
|||
|
|
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
|
|||
|
|
|
|||
|
|
|
|||
|
|
failures:
|
|||
|
|
tests::this_test_will_fail
|
|||
|
|
|
|||
|
|
test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|||
|
|
|
|||
|
|
error: test failed, to rerun pass `--lib`
|
|||
|
|
</code></pre>
|
|||
|
|
<h3 id="通过指定名字来运行部分测试"><a class="header" href="#通过指定名字来运行部分测试">通过指定名字来运行部分测试</a></h3>
|
|||
|
|
<p>有时运行整个测试集会耗费很长时间。如果你负责特定位置的代码，你可能会希望只运行与这些代码相关的测试。你可以向 <code>cargo test</code> 传递所希望运行的测试名称的参数来选择运行哪些测试。</p>
|
|||
|
|
<p>为了展示如何运行部分测试，示例 11-11 为 <code>add_two</code> 函数创建了三个测试，我们可以选择具体运行哪一个：</p>
|
|||
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|||
|
|
<pre><code class="language-rust noplayground">pub fn add_two(a: usize) -> usize {
|
|||
|
|
a + 2
|
|||
|
|
}
|
|||
|
|
|
|||
|
|
#[cfg(test)]
|
|||
|
|
mod tests {
|
|||
|
|
use super::*;
|
|||
|
|
|
|||
|
|
#[test]
|
|||
|
|
fn add_two_and_two() {
|
|||
|
|
let result = add_two(2);
|
|||
|
|
assert_eq!(result, 4);
|
|||
|
|
}
|
|||
|
|
|
|||
|
|
#[test]
|
|||
|
|
fn add_three_and_two() {
|
|||
|
|
let result = add_two(3);
|
|||
|
|
assert_eq!(result, 5);
|
|||
|
|
}
|
|||
|
|
|
|||
|
|
#[test]
|
|||
|
|
fn one_hundred() {
|
|||
|
|
let result = add_two(100);
|
|||
|
|
assert_eq!(result, 102);
|
|||
|
|
}
|
|||
|
|
}</code></pre>
|
|||
|
|
<p><span class="caption">示例 11-11：不同名称的三个测试</span></p>
|
|||
|
|
<p>如果没有传递任何参数就运行测试，如你所见，所有测试都会并行运行：</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test
|
|||
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|||
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.62s
|
|||
|
|
Running unittests src/lib.rs (target/debug/deps/adder-92948b65e88960b4)
|
|||
|
|
|
|||
|
|
running 3 tests
|
|||
|
|
test tests::add_three_and_two ... ok
|
|||
|
|
test tests::add_two_and_two ... ok
|
|||
|
|
test tests::one_hundred ... ok
|
|||
|
|
|
|||
|
|
test result: ok. 3 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>
|
|||
|
|
<h4 id="运行单个测试"><a class="header" href="#运行单个测试">运行单个测试</a></h4>
|
|||
|
|
<p>可以向 <code>cargo test</code> 传递任意测试的名称来只运行这个测试：</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test one_hundred
|
|||
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|||
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.69s
|
|||
|
|
Running unittests src/lib.rs (target/debug/deps/adder-92948b65e88960b4)
|
|||
|
|
|
|||
|
|
running 1 test
|
|||
|
|
test tests::one_hundred ... ok
|
|||
|
|
|
|||
|
|
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 2 filtered out; finished in 0.00s
|
|||
|
|
|
|||
|
|
</code></pre>
|
|||
|
|
<p>只有名称为 <code>one_hundred</code> 的测试被运行了；因为其余两个测试并不匹配这个名称。测试输出在摘要行的结尾显示了 <code>2 filtered out</code> 表明还存在比本次所运行的测试更多的测试没有被运行。</p>
|
|||
|
|
<p>不能像这样指定多个测试名称；只有传递给 <code>cargo test</code> 的第一个值才会被使用。不过有运行多个测试的方法。</p>
|
|||
|
|
<h4 id="过滤运行多个测试"><a class="header" href="#过滤运行多个测试">过滤运行多个测试</a></h4>
|
|||
|
|
<p>我们可以指定部分测试的名称，任何名称匹配这个名称的测试会被运行。例如，因为头两个测试的名称包含 <code>add</code>，可以通过 <code>cargo test add</code> 来运行这两个测试：</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test add
|
|||
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|||
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.61s
|
|||
|
|
Running unittests src/lib.rs (target/debug/deps/adder-92948b65e88960b4)
|
|||
|
|
|
|||
|
|
running 2 tests
|
|||
|
|
test tests::add_three_and_two ... ok
|
|||
|
|
test tests::add_two_and_two ... ok
|
|||
|
|
|
|||
|
|
test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.00s
|
|||
|
|
|
|||
|
|
</code></pre>
|
|||
|
|
<p>这运行了所有名字中带有 <code>add</code> 的测试，也过滤掉了名为 <code>one_hundred</code> 的测试。同时注意测试所在的模块也是测试名称的一部分，所以可以通过模块名来运行一个模块中的所有测试。</p>
|
|||
|
|
<h3 id="除非特别指定否则忽略某些测试"><a class="header" href="#除非特别指定否则忽略某些测试">除非特别指定否则忽略某些测试</a></h3>
|
|||
|
|
<p>有时一些特定的测试执行起来是非常耗费时间的，所以在大多数运行 <code>cargo test</code> 的时候希望能排除它们。虽然可以通过参数列举出所有希望运行的测试来做到，也可以使用 <code>ignore</code> 属性来标记耗时的测试并排除它们，如下所示：</p>
|
|||
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|||
|
|
<pre><code class="language-rust noplayground">pub fn add(left: usize, right: usize) -> usize {
|
|||
|
|
left + right
|
|||
|
|
}
|
|||
|
|
|
|||
|
|
// ANCHOR: here
|
|||
|
|
#[cfg(test)]
|
|||
|
|
mod tests {
|
|||
|
|
use super::*;
|
|||
|
|
|
|||
|
|
#[test]
|
|||
|
|
fn it_works() {
|
|||
|
|
let result = add(2, 2);
|
|||
|
|
assert_eq!(result, 4);
|
|||
|
|
}
|
|||
|
|
|
|||
|
|
#[test]
|
|||
|
|
#[ignore]
|
|||
|
|
fn expensive_test() {
|
|||
|
|
// 需要运行一个小时的代码
|
|||
|
|
}
|
|||
|
|
}
|
|||
|
|
// ANCHOR_END: here</code></pre>
|
|||
|
|
<p>对于想要排除的测试，我们在 <code>#[test]</code> 之后增加了 <code>#[ignore]</code> 行。现在如果运行测试，就会发现 <code>it_works</code> 运行了，而 <code>expensive_test</code> 没有运行：</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test
|
|||
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|||
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.60s
|
|||
|
|
Running unittests src/lib.rs (target/debug/deps/adder-92948b65e88960b4)
|
|||
|
|
|
|||
|
|
running 2 tests
|
|||
|
|
test tests::expensive_test ... ignored
|
|||
|
|
test tests::it_works ... ok
|
|||
|
|
|
|||
|
|
test result: ok. 1 passed; 0 failed; 1 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>expensive_test</code> 被列为 <code>ignored</code>，如果我们只希望运行被忽略的测试，可以使用 <code>cargo test -- --ignored</code>：</p>
|
|||
|
|
<pre><code class="language-console">$ cargo test -- --ignored
|
|||
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|||
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.61s
|
|||
|
|
Running unittests src/lib.rs (target/debug/deps/adder-92948b65e88960b4)
|
|||
|
|
|
|||
|
|
running 1 test
|
|||
|
|
test expensive_test ... ok
|
|||
|
|
|
|||
|
|
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1 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> 。当你需要运行 <code>ignored</code> 的测试时，可以执行 <code>cargo test -- --ignored</code>。如果你希望不管是否忽略都要运行全部测试，可以运行 <code>cargo test -- --include-ignored</code>。</p>
|
|||
|
|
|
|||
|
|
</main>
|
|||
|
|
|
|||
|
|
<nav class="nav-wrapper" aria-label="Page navigation">
|
|||
|
|
<!-- Mobile navigation buttons -->
|
|||
|
|
<a rel="prev" href="ch11-01-writing-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="ch11-03-test-organization.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="ch11-01-writing-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="ch11-03-test-organization.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="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>
|
|||
|
|
|
|||
|
|
<!-- Custom JS scripts -->
|
|||
|
|
<script src="ferris.js"></script>
|
|||
|
|
|
|||
|
|
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|