It’s been bothering me ever since that there’s no integration for unit tests in QtCreator. As I’m quite spoiled by the JUnit support in Eclipse IDE. Last summer I started to work on a tool that I call UnitTestMonitor. It’s not integrated into QtCreator yet, still I just released version 1.0.0 on github.
I . . . → Read More: UnitTestMonitor: Monitoring Qt unit tests
When coding with loops always take a few seconds to check what you can pull into loop initialization. Usually lists are not iterated only once so there’s a great opportunity for boosting performance. If you take the extra mile of calling QList::reserve(int) you can gain performance, too. . . . → Read More: Qt: QList and loop performance
While QtCreator is an excellent IDE for Qt projects it has no built-in support for unit testing and test coverage. In that article I’ll show you how to unit test your Qt application, automatically generate LCOV html coverage report and view them in a browser with just one click . . . → Read More: Generating LCOV Coverage with QtCreator
My fork of the Mousefeed Plugin has been merged with the Mousefeed Plugin available in Eclipse Marketplace. Please switch your update site to benefit from the most complete Mousefeed version. . . . → Read More: Eclipse Mousefeed Plugin Merged With Marketplace Plugin
Recently I joined a development team where a Qt/C++ thin client application is being developed. In December we decided to spend some time on improving unit test coverage. I did a PERT estimate and want to share my classification and estimation process hoping it will proof useful for you, too. . . . → Read More: Estimating Costs Of Unit Testing With Qt/C++
Developing UIs is a complex business. State machines can make your life easier when properly used. The Qt toolkit provides a simple State Machine Framework which neatly integrates with Qt widgets, signals and slots and the property system. However, it lacks support of naming states and the state machine and that’s not so nice when in need of debugging a state machine. So, in that post I’ll introduce you to my NamedStateMachine and NamedState as well as a NamedStateMachineInspector that you can use in unit tests or wherever you like. . . . → Read More: A Named QStateMachine
My Mousefeed plug-in fork has been merged with another fork available in the Eclipse Marketplace. . . . → Read More: Announcing: Mousefeed Plug-in 2.0.0
For most of the types in the Variables view you can see a reasonable toString() output below the variables list. However, many types don’t have a type specific implementation of toString(). That’s why the variables view prints you some meaningless default text with a hashcode for such variables. But did you know that you can change that by defining a custom toString() implementation that’s used by the variables view at runtime? Read on! . . . → Read More: Eclipse Tips & Tricks: Detail Formatter
Recently I was challenged getting declared commands enabled in an RCP application using own property testers. It seems the documentation of Eclipse’s Command Core Expressions framework is missing an important link that I’m gonna point out here.
RCP Application Plug-in
For this example create a new Plug-in project called de.rowlo.rcp.cce.app. Make sure to create a . . . → Read More: Eclipse Tips & Tricks: Property Testers with Command Core Expressions