Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

Unit testing setup #34

Open
stenbergd opened this issue May 7, 2015 · 3 comments
Open

Unit testing setup #34

stenbergd opened this issue May 7, 2015 · 3 comments
Milestone

Comments

@stenbergd
Copy link
Contributor

Is there a way where we can test some (all?) of the code functions through unit testing?

What would it require? Is there some standard method of unit testing embedded applications such as the one run on the STM32F3Discovery board?

Do we need to copy-paste function from target code to a separate C environment?

This could open up the possibility for Test-Driven development.

@stenbergd stenbergd added this to the Testing milestone May 7, 2015
@stenbergd
Copy link
Contributor Author

Currently working on system emulation with QEMU, which opens up possibilities to unit test greatly.

@stenbergd
Copy link
Contributor Author

How does unit test on real HW work? Does it need a dedicated build with different main method?

@adam-at-epsilon
Copy link
Contributor

I think we should add a stability test on hardware as well, perhaps if we could use a power source other than the battery (or two batteries), we could perhaps run the software for 2-3 hours in a row or preferably even longer.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants