Progress

Exams ended for me last tuesday, so I've had lots of time to code on xTest. I've done three major things the last couple of days:

• Upgrade looks to use Dolphins fade-in selection instead of checkboxes
  
• Make the CppUnit plugin run through an executable + parse xml back in
  
• Initial Check support
  

Couple of shots of the current state:

QTestLib runner prototype

An initial QTestlib runner is finished but still lacks severely:

• Real slow
  
• Feels KDE3'ish
  
• Static test registration
  

Slowness is the result of running a QTest executable for each of the test commands separately, instead of just once for each testcase. This'll obviously get fixed as soon as possible. Just to give you an idea: Kdevelop4's suite runs in about 3 seconds under CTest. The current plug in requires 30-ish ...

Second major flaw is looks. Especially the icons and combo box-tree are not up to standards. I'll probably use the test-status icons for selection as well (in front of the tests).

The actual test executable locations are still being read statically from XML. The location of this XML is, compiled in the hard way :) I'll sort this out by using the project configuration, the build API for test location and probably DUChain for suite structure detection.

To try it out yourself:

• Checkout kdevelop and kdevplatform from trunk
  
• De-comment the xtest plugin in kdevelop/plugins/CMakeLists.txt
  
• Adapt KDEV_HOME in kdevelop/plugins/xtest/xtestplugin.cpp:35
  
• Adapt the dir attribute of <root> in kdevelop/plugins/xtest/kdevtests.xml
  
• Build and install
  
• Fire up Kdevelop4 and add the xTest plugin through view->Add Tool View