Begin on implementing a robust UnitTesting system

[Norskan]

Incorperates Issues: #5 #16 #15 #14

• [x] collaps asserts to not duplicated logic
• [x] add a name for a test suite
• [x] asserts fail in unit tests should exit the test
• [x] silent run of tests
• [x] clean up output, one single point of output? Macros do not print anything but return struct with statuscode and error message if an error occured
• [x] New Assert Marcros
  • [x] UnitTest_Assert_True
  • [x] UnitTest_Assert_False
  • [x] UnitTest_Assert_MemoyCompaire
• [x] remove the first draft unit test functions and Asserts
• [x] convert the old unit tests to the new system
• [x] refactor to "Where there is one, there are many" idiologie
• [ ] document unit testing system

[Norskan]

First version of the Unittesting system is now implemented. There is only cleanup to do for the old style of tests.

@DaGrisa could you have a first look at it an give me a feedback if you have some additional addias for the system.

[DaGrisa]

Now that there is more and more functionality, i think we need to keep the Readme.md file up-to-date. Could be handled in a separate issue.

Edit: created new issue

[DaGrisa]

add .bat and .vscode to .gitignore

Edit: created new issue

[Norskan]

@DaGrisa can you test if the branch compiles und llvm ? i set some flags for the compiler and im not sure if they also work with llvm although normaly llvm is prete close to the gcc flags.

If not we need to override the cmake option once for gcc and once for llvm. I read an article about that and will link it if i find it

[Norskan]

@DaGrisa So im now more or less happy with the system. I simplified it a bit and reduced the number of function calls that are needed.

Could you have another look at it? If everything is alright i will write the "Documentation" and the branch can be merged.

[DaGrisa]

everything ok, nice work!