Update: The users of some a bit exotic SDKs reported that they cannot build the example. The reason was the project file SampleTest.mmp. I updated it making the project file a bit redundant. Now example should be compilable on any S60 SDK.
CppUTest is a unit testing framework based on CppUnitLite and designed for the embedded systems usage. Lately it has been ported to Symbian OS used in Nokia S60 smartphones. The framework is xUnit compatible, extremely simple and easy to use. It can print the test results both to console and to a junit-like xml file (later I am going to investigate how well it can be parsed by standard junit output parsers).
Symbian extension. Usage example
Unfortunately, CppUTest package at the moment does not include a full-blown Symbian specific example and lacks support for such Symbian primitives as descriptors (Symbian strings) and leaves (Symbian exceptions).
The file attached to this post contains both. It is a simple and heavily commented example of using CppUTest in Symbian, that includes cpputestsymbianextension.h adding support for descriptors and leaves.
Update on 09 Oct 2007: "See Also" section added
Bas Vodde collected and published examples and templates of the Scrum product and Sprint backlogs. Most of them are in MS Excel format. Some (XLS) include a lot of comments, some (XLS) are very colourful. Check them out, Excel can really cover most of the needs of the archived backlog tracking.
See Also
Today I've spent several hours trying to locate a simple example for the Nokia's Series 60 3rd edition. And miserably failed.
At the moment I am developing my first 3rd edition application. It is also the first app, where I am going to use vector icons in the svg format (introduced in Series 60 2nd edition Feature Pack 3). Somehow in all my previous projects I did the non-UI components only and never bothered about the application wrap-up.
Today in the morning I found that even though I have access to a lot of 3rd edition applications, I don't have a single simple example. As you might guess the attempts to "intelligently copy" the existing code failed.