Cross-platform software libraries and APIs
Qt Creator IDE and productivity tools
UI Design tool for UI composition
GUI test automation
Code coverage analysis
Test results management and analysis
Software static code analysis
Software architecture verification
The latest version of Qt.
Make the most of Qt tools, with options for commercial licensing, subscriptions, or open-source.
Explore Qt features, the Framework essentials, modules, tools & add-ons.
The project offers PySide6 - the official Python bindings that enhance Python applications.
Qt empowers productivity across the entire product development lifecycle, from UI design and software development to quality assurance and deployment. Find the solution that best suits your needs.
Insight into the evolution and importance of user-centric trends and strategies.
Learn how to shorten development times, improve user experience, and deploy anywhere.
Tips on efficient development, software architecture, and boosting team happiness.
Get the latest resources, check out upcoming events, and see who’s innovating with Qt.
Whether you're a beginner or a seasoned Qt pro, we have all the help and support you need to succeed.
October 29, 2010 by Yoann Lopes | Comments
If you are a contributor to Qt, you should know by now that your patches must not cause any regressions. The auto-tests in Qt (located in <QTDIR>/tests/auto) are there to ensure that. These tests are run automatically by the Qt Continuous Integration System before merging a staging branch into the mainline.
As a contributor, before submitting a merge request on Gitorious, you should always run locally the auto-tests related to what you are changing to simplify the reviewer's job. For instance, if you are patching something in QGraphicsView, you should compile and run individually 19 different auto-tests (the ones starting with 'qgraphics'). If you are used to that, you probably think that it is not the most pleasant and fast thing to do...
Well, let me introduce you Qt Autotester:
This handy little tool (that was used only internally until now) will help you in this process by making it a lot more simpler. Basically, you just select a set of auto-tests then the tool makes everything for you: it compiles, runs and shows you the results in a nice way.
The source is available here: http://qt.gitorious.org/qt-labs/qt-autotester
In a separate branch, I rewrote the UI with QtQuick and the Scenegraph to make it look even more fancy!
This project is of course open to suggestions and contributions. Enjoy!
Download the latest release here: www.qt.io/download.
Qt 6.8 release focuses on technology trends like spatial computing & XR, complex data visualization in 2D & 3D, and ARM-based development for desktop.
Check out all our open positions here and follow us on Instagram to see what it's like to be #QtPeople.
Oct 2, 2024
(Photo Credit: Friedemann Kleint) The Qt Contributor Summit is an annual..
Sep 20, 2024
Qt Gradle Plugin 1.0 (QtGP) build tool has been released. You can include..
Sep 16, 2024
We are happy to announce the release of Qt Tools for Android Studio 3.0...
Qt Group includes The Qt Company Oy and its global subsidiaries and affiliates.