如果当前循环没有发⽣元素交换，说明数组已经有序 if !swapped { break; } } } #[cfg(test)] mod tests { use super::*; #[test] fn test_empty_vec() { let mut empty_vec: Vec for x in bucket { result.push(x); } } result } #[cfg(test)] mod tests { use super::super::is_sorted; use super::*; #[test] fn empty() { let arr: } } if !swapped { break; } } } #[cfg(test)] mod tests { use super::*; #[test] fn basic() { let mut arr = vec![5, 2, 1, 3, 4, 6];

std::collections 中定义的所有公有项引入当前作用域。使用 glob 运算符 时请多加小心！Glob 会使得我们难以推导作用域中有什么名称和它们是在何处定义的。 glob 运算符经常用于测试模块 tests 中，这时会将所有内容引入作用域；我们将在第十一章 “如何编写测试” 部分讲解。glob 运算符有时也用于 prelude 模式；查看 标准库中的文档 了解 这个模式的更多细节。 162/600 试和集成测试。 240/600 Rust 程序设计语言 简体中文版 1 1 . 1 . 如 何 编 写 测 试 如何编写测试 ch11-01-writing-tests.md commit 6e2fe7c0f085989cc498cec139e717e2af172cb7 Rust 中的测试函数是用来验证非测试代码是否是按照期望的方式运行的。测试函数体通常执 行如下三种操作： #[cfg(test)] mod tests { #[test] fn it_works() { let result = 2 + 2; assert_eq!(result, 4); } } 241/600 Rust 程序设计语言 简体中文版 示例 11-1：由 cargo new 自动生成的测试模块和函数 现在让我们暂时忽略 tests 模块和 #[cfg(test)]

std::collections 中定义的所有公有项引入当前作用域。使用 glob 运算符时 请多加小心！Glob 会使得我们难以推导作用域中有什么名称和它们是在何处定义的。 glob 运算符经常用于测试模块 tests 中，这时会将所有内容引入作用域；我们将在第十一 章“如何编写测试”部分讲解。glob 运算符有时也用于 prelude 模式；查看标准库中的文档了解 这个模式的更多细节。 149/562Rust 文件名：src/lib.rs pub fn add(left: u64, right: u64) -> u64 { left + right } #[cfg(test)] mod tests { use super::*; #[test] fn it_works() { let result = add(2, 2); assert_eq 220/562Rust 程序设计语言 简体中文版 现在让我们只关注 it_works 函数本身。注意 fn 行之前的 #[test]：这个属性表明这是一个测 试函数，这样测试执行者就知道将其作为测试处理。tests 模块中也可以有非测试的函数来帮 助我们建立通用场景或进行常见操作，必须每次都标明哪些函数是测试。 示例函数体通过使用 assert_eq! 宏来断言 result（其中包含 2 加 2 的结果）等于

thanks to this change. 在 Kotlin/Native 中能够为 iOS 模拟器测试配置独立模 式 By default, when running iOS simulator tests for Kotlin/Native, the --standalone flag is used to avoid manual simulator booting and shutdown Android and common tests The new Android source set layout changes the relation between Android- instrumented tests (renamed to androidInstrumentedTest in the new layout) and common tests. Previously, corresponding actual implementations in androidAndroidTest . Tests declared in commonTest were also running as Android instrumented tests. In the new Android source set layout, the dependsOn relation

covered in detail later in the course. An expression can be ”boxed” with Box::new as seen in the tests. To evaluate a boxed expression, use the deref operator (*) to ”unbox” it: eval(*boxed_expr). Some BinaryTree { root: Subtree, } // Implement `new`, `insert`, `len`, and `has`. mod tests { use super::*; fn len() { let mut tree = BinaryTree::new(); assert_eq!(tree.len(), 0); tree.insert(2); insert("foo"); assert_eq!(tree.len(), 1); tree.insert("bar"); assert!(tree.has(&"foo")); } mod tests { use super::*; fn len() { let mut tree = BinaryTree::new(); assert_eq!(tree.len(), 0); tree.insert(2);

thanks to this change. 在 Kotlin/Native 中能够为 iOS 模拟器测试配置独立模式 By default, when running iOS simulator tests for Kotlin/Native, the --standalone flag is used to avoid manual simulator booting and shutdown Android and common tests The new Android source set layout changes the relation between Android-instrumented tests (renamed to androidInstrumentedTest in the new layout) and common tests. Previously, there corresponding actual implementations in androidAndroidTest . Tests declared in commonTest were also running as Android instrumented tests. In the new Android source set layout, the dependsOn relation

md,readme}",, "!**/node_modules/*/{test,__tests__,tests,powered-test,example,examples}" "!**/node_modules/*/{test,__tests__,tests,powered-test,example,examples}",, "!**/node_modules/* README,readme.md,readme}",, "!**/node_modules/*/{test,__tests__,tests,powered-test,example,examples}" "!**/node_modules/*/{test,__tests__,tests,powered-test,example,examples}",, "!**/node_modules/*.d md,readme}",, "!**/node_modules/*/{test,__tests__,tests,powered-test,example,examples}" "!**/node_modules/*/{test,__tests__,tests,powered-test,example,examples}",, "!**/node_modules/*

生成延迟测试失败报告 15.6. 生成 JUNIT 延迟测试报告 15.7. 在单节点 OPENSHIFT 集群上运行延迟测试 15.8. 在断开连接的集群中运行延迟测试 15.9. 对 CNF-TESTS 容器的错误进行故障排除 78 78 78 80 80 82 83 84 87 87 87 90 90 92 92 94 94 94 95 96 96 96 100 "disable" spec: containers: - name: dynamic-irq-pod image: "registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10" command: ["sleep", "10h"] resources: requests: cpu: 2 memory: 集群上运行延迟测试，其中安装了运行 CNF 工作负载所需的所有组件。运行延迟测试以验证工 作负载的节点调整。 cnf-tests 容器镜像位于 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 中。 重要 重要 cnf-tests 镜像还包含了红帽不支持的多个测试。红帽只支持延迟测试。 15.1. 运行延迟测试的先决条件 运行延迟测试前，集群必须满足以下要求：

Following document assumes that sbuild is configured this way. Edit this to your needs. Post-build tests can be turned on and off by assigning 1 or 0 to the corresponding variables, Warning 可选的自定义项可能造成负面影响。如果有疑问，请禁用它们。 ra1source/format I: creating => debian/source/format I: substituting => /usr/share/debmake/extra1tests/control I: creating => debian/source/control I: substituting => /usr/share/debmake/extra1upstream/metadata creating => debian/upstream/metadata I: substituting => /usr/share/debmake/extra1tests/control I: creating => debian/tests/control I: substituting => /usr/share/debmake/extra1patches/series I: creating =>

you want to do other things when building Krita. tests ‒ Whether you want to build tests. On Windows many of them are broken, so you can disable tests by setting this variable to 0. It is suggested to KRITA_DEVS PYQT_SIP_DIR_OVERRIDE USE_LOCK_FREE_HASH_TABLE FOUNDATION_BUILD KRITA_ENABLE_BROKEN_TESTS LIMIT_LONG_TESTS ENABLE_PYTHON_2 BUILD_KRITA_QT_DESIGNER_PLUGINS BUILD_TESTING If set to ON, the unittests KRITA_ENABLE_BROKEN_TESTS A number of unittests are known to be broken. They should be fixed, but in the meantime, having dozens of failing unittests hides regressions. Set this to ON to run the broken tests. These