FrogBlog

This week #QtDD12 have been held in Berlin. It was a great event and clearly shows that the future of Qt as cross platform development framework looks very bright again.

On the first day a Squish training course has been held by KDAB, which was very well attended. We have seen lots of interest in Squish GUI Tester and Squish Coco ar our booth in the expo area and the talks about Squish and Squish Coco yesterday were also very well attended.

In two weeks the US Qt Developer Days will take place in Santa Clara and we are already looking forward to being there as well.

Many thanks to KDAB and ICS for the initiative and organization and to Digia for co-hosting a wonderful event!

froglogic is proud to sponsor the Qt Developer Days in Berlin, Germany, on November 12-14th and Santa Clara, California, on December 5-7th: www.qtdeveloperdays.com

In addition to the technical tracks and workshops focusing on software development with Qt, the estimated 400-500 participants will be able to take advantage of the Squish Training Class on the first day of the event that will show how to do automated testing of Qt based applications with Squish for Qt.

froglogic will also have a booth in the exhibition area and froglogic’s founders will give talks about the Squish GUI Tester and the Squish Coco code coverage tool.

We look forward to seeing you there!

Our partner KDAB, who is a Squish expert providing services around Squish and Qt, and who has helped many of our customers with their GUI test automation, published a new monthly Squish tip.

Read it at Remember_nativeType

All of KDAB’s tips can be read at QDN Squish

We are hiring. See our job ad at StackOverflow. In addition we need technical documentation writers and technical sales people.

Contact us at jobs@froglogic.com if you are interested!

Squish supports automating iOS Apps on the Simulator and on devices for several years now. In addition, we are close to releasing Squish for Android.

You can now see a demo video of how Squish works to automate iOS Apps at YouTube.

The last exhibition day of 3 days total at the BASTA! conference is about to end. It’s the first time that we have chosen to come here and it turned out be a worthwhile trip. The BASTA! conference including two days of workshops centers around .NET, Visual Studio, Team Foundation Server (TFS), WPF and other topics related to the Microsoft Windows platform. This made the event a good place to show our still to be announced integration into Visual Studio, TFS and Microsoft Test Manager (MTM) in public for the first time.

Read the rest of this entry »

… not just testers. While our products Squish and Squish Coco are about testing we also need developers! Good ones. Those that are good with C++ mainly. But in the end we can also throw Java, ObjectiveC, C#, Python, JavaScript, Perl, PHP and Tcl in the mix if you want to work on one of the editions of our products.

With Nokia step-by-step retracting from Qt the development scene is going to change. Nokia needs to be applauded for what they’ve done to the product. But Qt has outgrown what a single vendor can provide. Partially, because the needs of its users are so diverse. As part of putting development of the core product and add-ons on more shoulders we are among those companies that are open to hire some more ex-Trolls and Nokians.

A question to those out there who are interested in the use of revision control software and release management. We are using git but I’ll try to formulate the challenge independant of the concrete system.

For quite some time now we are using a dedicated release branch in order to decouple work on a software release from ongoing development and maintenance work. This helps a lot to allow for stabilization, testing, preparing of release notes, etc., without interrupting everyone else’s bugfixing and feature implementation work. Patches picked for the release are taking from the maintenance version branch. That branch is already considered stable but as we all know: some patches are more stable than others

The work done at this level is not necessarily that of a classic patch review where a developer requests the integration of a patch that might be accepted, changed or rejected. It’s a selection process where fixes are judged by their importance and an assessment of the benefit vs. risk. A change not accepted in this process will not necessarily dropped completely. It’ll just have to wait until the next release.

What I’ve been wondering: anyone knows any good tools that feature a selection process of this type? We’ve briefly looked at Gerrit and Crucible (impressive patch reviewing capabilities!) but I can’t help but feeling that they are geared towards another work flow. It’s not about developers filing merge requests that are either accepted or denied. It’s about a post-commit selection process among candidate commits. Commands like git cherry help to determine unmerged changes. But some frontend that provides a good overview, allows for comments and remembers do-not-merge decisions for specified branches would be very nice to have. Any suggestions? Any way to set up of the wide spread systems to do what I’m looking for? Thanks.

PS: Despite using the term “cherry picking” we are not settled on this particular feature. If regular branches and merges can be used without too much pain that’s also fine.

Another “best year ever” at froglogic slowly comes to an end. We’d like to take the opportunity to thank all our customers and partners for the trust you put in us and look forward to continue working with you in 2012.

Here is a team photo we took at our Christmas Party last week where we toured the Elbe river, harbor and new “Hafen-City” with a barge.

Merry Christmas and a Happy New Year 2012!

Your froglogic Team

After an eventful year in the Qt world it’s time for the annual Qt Developer Days again. We are very happy that the tradition continues and as it looks the European event, which starts today in Munich, will be more than well attended.

If you are at dev days too, make sure to drop by at our booth to see what’s new in Squish for Qt and beyond. #qtdd11