[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-cim] Testing update


  • To: <xen-cim@xxxxxxxxxxxxxxxxxxx>
  • From: "Szymanski, Lukasz K" <Lukasz.Szymanski@xxxxxxxxxx>
  • Date: Tue, 17 Apr 2007 15:36:02 -0400
  • Delivery-date: Tue, 17 Apr 2007 12:34:38 -0700
  • List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
  • Thread-index: Acd9JuF+YOTY3R6ZTay3mtpX5z+MxAD+lMmA
  • Thread-topic: Testing update

I have put together a bash script which constructs the xml input file
for most of the cimtester (intrinsic) tests: EnumInstances,
Associations, References, GetInstance, Sanity, EnumInstanceNames,
AssociatorNames, ReferenceNames.  I can explain the details of how it
works in a README file.  The test results are not very spectacular;
sanity test was the most insightful in terms of where we need to work.
I will post all the test results and their explanations in another
email.

Jim, in response to your question about calling external tests - yes,
that can definitely be done.  I successfully called a python script from
within cimtester.  In fact, I called your python script up to the point
of defining a vm, and then invoked the
Xen_ComputerSystem.RequestStateChange method to start it via internal
cimtester methods.  I also cleaned up the python script a bit, added
some print statements for clarity and some comments in case anyone else
wanted to pick this up.  I am attaching it here in case you want to use
any of it.

I suggest we add a testing directory to the main tree and put all the
relevant stuff in there - that's how I have it set up on my box.

Luke

Attachment: test.py
Description: test.py

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.