Running and Exporting Test Results from Ceedling Running a Ceedling test on the local development workstation. The content in this blog post was developed based on the following software versions: The blog post will be updated when that PR has been merged to master. A PR has been submitted to add coverage reporting via xml output, but this blog shows how to hack the 0.28.3 branch to get this working. While it is quite capable, there are some areas lacking documentation, which required us to tinker under the hood to complete our integration.Īn important caveat: this blog post reflects Ceedling 0.28.3, released on 8th August, 2018. I’m also reading James Grenning’s book Test Driven Development for Embedded C.Ĭeedling is still pre-1.0 as of February 2019. His field manual enabled us to quickly understand and start using these testing tools. If you are new to Ceedling (or even unit testing in general, like I am) I recommend Matt Chernosky’s eBook A Field Manual for Ceedling. This post focuses on the less straightforward step of capturing the unit testing results and reporting them to Jenkins. Ceedling works well on our developer workstations in Eclipse and command prompts, and it was also straight forward to get running on our build server (Jenkins running on Ubuntu). We chose Ceedling+Unity for our unit testing framework, in part because of its strong integration with the Eclipse IDE. Unit testing is another best practice that we have embraced, and we are working to cover as much of our embedded code as possible. We used this method at Benchmark Space Systems to add a firmware version to our project. In the last post, we shared a method for implementing custom build steps in the Eclipse IDE. He has spent time in the Aerospace, Consumer Audio, and Integrated Circuits fields, more often than not working at the intersection of hardware and software. Paul is the Lead Electrical Engineer at Benchmark Space Systems. Today we have another guest post by Paul Shepherd, this time covering integration of Ceedling and Unity with the build status reporting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |