Testing

• It's always better to test boot every time you make a system change, because it is important to see how the OS boots and works after it compiles.

• Even though Rust is a safety-oriented language, something as unstable and low-level as a work-in-progress operating system will almost certainly have problems in many cases and may completely break on even the slightest critical change.

• Also, make sure you verified how the unmodified version runs on your machine before making any changes. Else, you won't have anything to compare to, and it will generally just lead to confusion. TLDR: rebuild and test boot often.

• The real hardware testing is bigger than QEMU testing and thus detect more bugs

• There's also the acid test suite from Redox, to use it run the make rp.acid command from the build system to install the suite in the Redox image, run the cd acid command to go to the acid directory and use the cargo test command to run correctness tests and cargo bench command to run stress tests.

• The relibc test suite is used to complement acid, use the make r.relibc-tests-bins command from the build system to run it or the make rp.relibc-tests command to add the source in the Redox image, build (cd relibc-tests and make run commands) and run it (make test command) later inside of Redox for more testing.

• The os-test test suite has the largest number of tests and is the recommended method to test the system, use the make r.os-test-bins command from the build system to run it or the make rp.os-test command to add the source in the Redox image, build (cd os-test and make all commands) and run it (make test command) later inside of Redox for more testing.