From 22470e7c8750008e2734ce7029403cec01bfc697 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Wed, 27 Jun 2018 12:22:00 +0200 Subject: [PATCH] =?UTF-8?q?Fix:=20should=20be=20=E2=80=9Cintegration=20tes?= =?UTF-8?q?t=E2=80=9D=20instead=20of=20=E2=80=9Cunit=20test=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../second-edition/posts/05-integration-tests/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blog/content/second-edition/posts/05-integration-tests/index.md b/blog/content/second-edition/posts/05-integration-tests/index.md index 819dd7ff..3856ae2f 100644 --- a/blog/content/second-edition/posts/05-integration-tests/index.md +++ b/blog/content/second-edition/posts/05-integration-tests/index.md @@ -321,7 +321,7 @@ A better solution is to create an additional executable for each test. ### Additional Test Executables -Cargo allows to add [additional executables] to a project by putting them inside `src/bin`. We can use that feature to create a separate executable for each unit tests. For example, a `test-something` executable could be added like this: +Cargo allows to add [additional executables] to a project by putting them inside `src/bin`. We can use that feature to create a separate executable for each integration test. For example, a `test-something` executable could be added like this: [additional executables]: https://doc.rust-lang.org/cargo/reference/manifest.html#the-project-layout @@ -577,7 +577,7 @@ Such a test runner is useful to many projects, so we decided to add one to the ` The test runner of the `bootimage` tool can be invoked via `bootimage test`. It uses the following conventions: -- All executables starting with `test-` are treated as unit test. +- All executables starting with `test-` are treated as integration tests. - Tests must print either `ok` or `failed` over the serial port. When printing `failed` they can print additional information such as a panic message (in the next lines). - Tests are run with a timeout of 1 minute. If the test has not completed in time, it is reported as "timed out".