Now, The VDSM test unit is expected to run in a un-installed enviornment
and use hackVDSM() to fake modules importing. hackVDSM() is pretty
tricky for other modules to be added because of the dependency order. I
would propose to run the VDSM unit tests in a installed VDSM path which
is the same path as other VDSM runnable binaries. By this way, we can
abandon hackVDSM() and run the unit test normally. On the other hand,
the VDSM building script installs the VDSM files to <home>/builder by
default, it is reasonable to start the VDSM unit test after all parts of
the building script finishes. Any comments about this idea?
舒明 Shu Ming
Open Virtualization Engineerning; CSTL, IBM Corp.
Tel: 86-10-82451626 Tieline: 9051626 E-mail: shum...@cn.ibm.com or
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
vdsm-devel mailing list