Hi Pradeep, On 07/26/2012 04:57 PM, Pradeep Kumar Surisetty wrote: > How about opening an issue in autotest issue tracker before starting > automation or send RFC, such that we dont duplicate our effort. > I'm glad you have such a good idea. :)
Besides vcpupin, there are about 70 virsh commands' tests we have developed. All the test programs works fine, but the style is not good enough because we did all this work based on an old autotest. And some of our tests have been applied, such as migrate, hostname, and so on. To avoid duplicating our efforts, maybe I can give you a list of our work. BTW, I am not quite familiar with issue tracker. How to build one ? Would you please help to build it ? Thanks. :) Here is the list of the commands we are testing. domname schedinfo attach-interface detach-interface setmem setmaxmem setvcpus attach-disk detach-disk domjobabort attach-device detach-device vcpupin update-device undefine edit shutdown suspend start reboot restore save destroy managedsave domxml-from-native domxml-to-native domjobinfo dommemstat domifstat domstate domblkinfo domblkstat console ttyconsole vcpuinfo vncdisplay migrate-setmaxdowntime dominfo domid domuuid resume net-create net-define net-destroy net-dumpxml net-name net-uuid net-start net-undefine net-autostart net-list nodedev-dettach nodedev-dumpxml cpu-compare cpu-baseline list dumpxml dump quit help connect -- Best Regards, Tang chen _______________________________________________ Autotest mailing list Autotest@test.kernel.org http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
