ToDo/QMPTesting

From QEMU
Revision as of 21:43, 11 October 2010 by LuizCapitulino (talk | contribs) (Created page with '= QMP Testing TODO = This page describes the work to be done on improving QMP test coverage and quality. We have the following tools/framework available: * QEMU's unit-tests * …')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

QMP Testing TODO

This page describes the work to be done on improving QMP test coverage and quality. We have the following tools/framework available:

  • QEMU's unit-tests
  • kvm-autotest
  • libvirt-TCK

unit-tests

C level testing, used to check QEMU's internal APIs.

Currently we have a good coverage of QObjects types (QInt, QString, etc) and the JSON parser. We need to test as much Monitor code as possible, however there are two difficulties associated with this:

  1. Monitor code is not modular and has not been designed with unit-tests in mind
  2. It's unlikely that it will be possible to test handlers code this way, as most of them depends on other subsystems

Item 1 will be solved when the current monitor redesign work is finished.

TODO:

  1. Fix problems in current unit-tests (try compiling and running them to see what happens)
  2. Introduce a unit-test tree structure in QEMU
  3. Add a 'make test' target, which runs *all* QEMU's unit-tests
  4. Add unit-tests for new monitor code

kvm-autotest

libvirt-TCK