Overview
ZestCode should have a suite of integration tests that verify the correctness of the device API and RTOS. (I've excluded mention of unit tests because I don't believe most parts of the kernel would benefit from unit testing, but they can be added if needed.)
Motivation
Having a comprehensive suite of tests prevents bugs and regressions. Also needed for #39.
Additional Information
Ideally, each integration test should have a machine readable section that describes the hardware layout needed for the test, to facilitate integration with vex-v5-qemu in the future.
Overview
ZestCode should have a suite of integration tests that verify the correctness of the device API and RTOS. (I've excluded mention of unit tests because I don't believe most parts of the kernel would benefit from unit testing, but they can be added if needed.)
Motivation
Having a comprehensive suite of tests prevents bugs and regressions. Also needed for #39.
Additional Information
Ideally, each integration test should have a machine readable section that describes the hardware layout needed for the test, to facilitate integration with vex-v5-qemu in the future.