Basic custom #[no_std] test runner

[RyanKoech]

EDIT - See original below

Set up basic custom runner powered by makefiles. Use make test

ORIGINAL - from when PR was a Draft PR WIP

Global search the code for 'RYANS_NOTES' to see notes i've written.

There's issues running tests.
cargo test produces the error below:

error: unwinding panics are not supported without std

  = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
  = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem

warning: `hexium_os` (bin "hexium_os" test) generated 1 warning
error: could not compile `hexium_os` (bin "hexium_os" test) due to 1 previous error; 1 warning emitted
warning: build failed, waiting for other jobs to finish...
error[E0152]: duplicate lang item in crate `core` (which `std` depends on): `sized`

I fixed this by using the command cargo test --target x86_64-unknown-none
Then I got the error below where I'm stuck at.

error[E0463]: can't find crate for `test`

error: `#[panic_handler]` function required, but not found

[RyanKoech]

So the commit 9e060bb has fixed the build issue, and everything seems to be building fine.

A new error is being experienced however

    Finished `test` profile [unoptimized + debuginfo] target(s) in 33.88s
     Running unittests src/lib.rs (target/x86_64-unknown-none/debug/deps/hexium_os-ff3ea686c9bc2f62)
error: test failed, to rerun pass `--lib`

Caused by:
  process didn't exit successfully: `/../Hexium/kernel/target/x86_64-unknown-none/debug/deps/hexium_os-ff3ea686c9bc2f62` (signal: 11, SIGSEGV: invalid memory reference)

[RyanKoech]

closes #2

[RyanKoech]

Note: That a timeout has not been implemented into the tests yet, so this could lead to indefinite running tests. Could have its issue ticket set up for later.

@HexiumOS/core-developers

[RyanKoech]

Note: That a timeout has not been implemented into the tests yet, so this could lead to indefinite running tests. Could have its issue ticket set up for later.

So we've decided we'll create a new issue for this.

Edit: Issue #29

[RyanKoech]

Furthermore, we've also decided we'll leave out the executor code out for now, to be reintroduced in the future. An issue will be put up for this.

Issues #30

[RyanKoech]

Another issue will also be created for testing println output. Issue #31

[RyanKoech]

Another issue to complete the test/writer.rs tests for testing println out put has also been created. Issue #31

[RyanKoech]

@HexiumOS/core-developers PR is ready for review