QtCS25 - QtTest: state of the module and the way forward
Jump to navigation
Jump to search
Session Summary
- People are using TestLib, pain points, wishes and how to improve it.
Session Owners
Tor Arne
Notes
- Testlib is used to test Qt itself but also by others to test their project
Wishes/Pain points
- Behavior-driven development (see catch - used to test Testlib itself) - using more natural like language
- specifying set-up, preconditions the actual test
- better way for data driven tests compared to current rows/columns
- Be able to use <code>QVERIFY</code> and friends outside test functions (can use exceptions currently)
- Improving integration with QtQuickTest
- Mocking
- Update docs
- No cleanup
- Dependent on Meta Object System => inefficient, tightly coupled to Qt
- testing the QPA layer is hard
- Other testing paradigms exist but do not reinvent the wheel, decouple things like event loop handling and QVERIFY so it can integrate into other harnesses