Posted on May 22, 2018 at 04:18On my current project I'm using Visual Studio 2017 for most application level code. I'm using it because it provides a very fast build/debug cycle vs trying to do something on target. The motivation for using VS is to make running the tests as effortless as possible. The easier it is to run the tests the more often you'll run them, and the more confidence you will have when refactoring. Also, the VS environment understands you are running tests and gives you nice point and click options like running only a specific test and a clean display of which tests passed and which failed.
File->New Project->Visual C++->Test->Native Unit Test Project
In Visual Studio, low level driver stuff has to be mocked out of course (but even if you're doing it on target drivers often need to be mocked out so you can control them). I'm sure I will end up needing to write some driver tests to run on the target, but these should need to be updated much less often.
Is using a different compiler on different hardware going to end up biting me? I don't know yet. But so far I've been quite happy with it.
I have used Unity before with success on target. Only real issue was limited flash space on the target. I had to break the tests into many different parts and build and run each one separately which was slow.
