michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-16 22:37:49 +00:00
Code Issues Projects Releases Wiki Activity

Fix typo in 04-testing (#654)

Browse Source
This commit is contained in:
Nikos Fertakis
2019-08-10 12:17:19 +03:00
committed by Philipp Oppermann
parent 4b3fbd27cc
commit f4123dc011
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
blog/content/second-edition/posts/04-testing/index.md
View File

@@ -884,7 +884,7 @@ use blog_os::{QemuExitCode, exit_qemu, serial_println};
#[no_mangle] #[no_mangle]
pub extern "C" fn _start() -> ! { pub extern "C" fn _start() -> ! {
should_panic(); should_fail();
serial_println!("[test did not panic]"); serial_println!("[test did not panic]");
exit_qemu(QemuExitCode::Failed); exit_qemu(QemuExitCode::Failed);
loop{} loop{}
@@ -903,7 +903,7 @@ fn panic(_info: &PanicInfo) -> ! {
} }
``` ```
We now call the `should_panic` function directly from our `_start` function and exit with a failure exit code if it returns. When we run `cargo xtest --test should_panic` now, we see that the test behaves exactly as before. We now call the `should_fail` function directly from our `_start` function and exit with a failure exit code if it returns. When we run `cargo xtest --test should_panic` now, we see that the test behaves exactly as before.
Apart from creating `should_panic` tests, disabling the `harness` attribute can also be useful for complex integration tests, for example when the individual test functions have side effects and need to be run in a specified order. Apart from creating `should_panic` tests, disabling the `harness` attribute can also be useful for complex integration tests, for example when the individual test functions have side effects and need to be run in a specified order.