Test driving-qml

Test driving-qml

• 1.
  Test-Driving QML Helsinki Artem Marchenko Helsinki Qt Meetup May 15, 2012
• 2.
  Artem Marchenko http://fi.linkedin.com/in/artemmarchenko
• 3.
  Test-Driven Development. Orjust testing QML • What TDD is about • Getting started • Simple Synchronous test • Simulating mouse and keyboard actions • Asynchronous tests (verifying callbacks) • Data-driven tests • Current limitations • Q&As
• 4.
  Test-Driven Development
• 5.
  Example of aQML-code developed via TDD
• 6.
  Getting started 1(3) gitclone git://gitorious.org/qt-labs/qtest-qml.git Cloning into qtest-qml... remote: Counting objects: 888, done. remote: Compressing objects: 100% (669/669), done. remote: Total 888 (delta 445), reused 393 (delta 187) Receiving objects: 100% (888/888), 411.11 KiB, done. Resolving deltas: 100% (445/445), done. cd qtest-qml/ qmake qtest-qml.pro make make install make docs make check Project page: http://qt.gitorious.net/qt-labs/qtest-qml
• 7.
  Getting started 2(3) •Create the simplest test in your project
• 8.
  Getting started 3(2) •And a script that runs the test: runTests.sh in this case #!/bin/bash clear /Users/artem/QtSDK/Desktop/Qt/471/gcc/bin/QMLViewer.app/Contents/MacOS/QML Viewer tst_tddCalculator2.qml
• 9.
  Simple synchronous tests
• 10.
  UI level: simulatingmouse click
• 11.
  UI level: simulatingtouch and drag
• 12.
  Asynchronous testing: tryCompare
• 13.
  Asynchronous testing: SignalSpy
• 14.
  Data-driven tests
• 15.
  Current Limitations • Installationdoesn’t install qtest-qml to QtCreator – Not that you would need it for TDD, but if you are into “just testing” already written code, debugger may be helpful • Bug: only one TestCase is allowed: http://bugreports.qt.nokia.com/browse/QTBUG-17200 (possibly fixed for 4.8) – It makes init() and cleanup nearly useless – Organize your test structure by your own tools • Small difficulties comparing built-in classes (e.g. color) – toString() helps most of the time
• 16.
  Current limitations • Verystrange errors when object/property can be accessed e.g. because of a typo • Segmentation faults, sometimes even “file not found” • In 95% of cases that is a typo or an attempt to access a non-public property
• 17.
  Current limitations • SignalSpycan only count – It cannot examine the signal arguments or the state of other objects. Is supposed to be fixed for Qt 5.0 • Benchmarking is a part of a qtest-qml, but doesn’t work properly – That is I failed to make it run for a given amount of times (most of the time it does just a single run) • No built-in device test runners – Though you can certainly, embed a “run tests” button right into your application
• 18.
  My company TwineLABOy • Startup with proven financing • We need more people excited about high quality software and bringing end-to-end products to people • Buzzwords: – Qt/QML – Linux platform – high quality SW – video/audio codecs – server-side Java / GWT – large-scale metrics [email protected]
• 19.
  Q&As time Youcan find these [and nearly identical older version of the same] slides at http://agilesoftwaredevelopment.com/tags/tdd Further contacts: http://fi.linkedin.com/in/artemmarchenko [email protected]