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

Update release date

Browse Source
This commit is contained in:
Philipp Oppermann
2018-04-29 22:52:38 +02:00
parent 547943bb94
commit 94c3b63ff6
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -2,7 +2,7 @@
title = "Unit Testing" title = "Unit Testing"
order = 4 order = 4
path = "unit-testing" path = "unit-testing"
date = 2018-04-14 date = 2018-04-29
template = "second-edition/page.html" template = "second-edition/page.html"
+++ +++
@@ -392,6 +392,3 @@ We also learned a bit about conditional compilation, Rust's [lint system], how t
We now have a working unit testing framework, which gives us the ability to test individual components. However, unit tests have the disadvantage that they run on the host machine and are thus unable to test how components interact with platform specific parts. For example, we can't test the `println!` macro with an unit test because it wants to write at the VGA text buffer at address `0xb8000`, which only exists in the bare metal environment. We now have a working unit testing framework, which gives us the ability to test individual components. However, unit tests have the disadvantage that they run on the host machine and are thus unable to test how components interact with platform specific parts. For example, we can't test the `println!` macro with an unit test because it wants to write at the VGA text buffer at address `0xb8000`, which only exists in the bare metal environment.
The next post will close this gap by creating a basic _integration test_ framework, which runs the tests in QEMU and thus has access to platform specific components. This will allow us to test the full system, for example that our kernel boots correctly or that no deadlock occurs on nested `println!` invocations. The next post will close this gap by creating a basic _integration test_ framework, which runs the tests in QEMU and thus has access to platform specific components. This will allow us to test the full system, for example that our kernel boots correctly or that no deadlock occurs on nested `println!` invocations.
## NOTES
TODO update date