Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • answers are expected to stand on their own. Forcing readers to get to external resource to find out substance is frowned upon at Stack Exchange ("read the article or check out Ceedling"). Consider editing to make it fit site quality norms Commented Jan 28, 2016 at 2:07
  • Does Ceedling have any mechanisms to support asynchronous events? One of the more challenging aspects of real-time embedded applications is that they deal with receiving inputs from very complex systems that are themselves difficult to model... Commented Feb 16, 2016 at 19:36
  • @Jay It doesn't have anything specifically to support that. However I've had success testing that sort of thing with mocking, and by setting up an architecture to support it. For example, I recently worked on a project where interrupt-driven events were put into a queue and then consumed in an "event handler" state machine. This was essentially just a function that was called whenever an event occurred. When testing that function, I could mock the function call that pulled events out of the queue, and so could simulate any event occurring in the system. Test driving helps here too. Commented Feb 18, 2016 at 5:47