| |
|
 |
|
 |
|
|
|
| |
|
|
xen-cim
[Xen-cim] RE: Test Suite Structure
Jim -
The situation is this:
1089:/tmp/test/cmpi/os-cmpi-xen.hg/test # ls
README embed_inst_kernel.py
instance_provider_template system
association_provider_list run-test.sh xm-test
association_provider_template instance_provider_list setup-test.sh
There are several intrinsic files, directories, and two scripts -
run-test.sh and setup-test.sh all needed by the sblim-test suite.
The extrinsic test has its own test.py file (currently
embed_inst_kernel.py) plus a directory (currently xm-test) which is
where the xm-test ramdisk stuff resides. I guess what I'm wondering is,
if there should be one test to run the intrinsics stuff and a separate
one to run the extrinsic stuff. If there should be one big
run_everything.sh file which kicks of the intrinsic and extrinsic tests
then it makes sense to keep everything in one directory. Otherwise,
it's hard to say what's what. I don't really care what we do, I just
want to know which way to go.
Luke
-----Original Message-----
Szymanski, Lukasz K wrote:
> Jim -
>
> What are your thoughts on moving all the intrinsic test files to a new
> intrinsic directory, and doing the equivalent for the extrinsics? At
> this point it could get confusing which files belongs where.
>
Hmm, not sure. I was browsing the various sblim projects for and
indication of best practices but could not correlate what I saw there
with your question. Perhaps Gareth has some experience in this area and
can provide suggestions.
Is the problem that you need different input files for instrinsics vs
extrinsics? E.g. is there a Xen_ComputerSystem.system file for
intrinsic ops and another for extrinsic? One file cannot support both
intrinsic and extrinsic ops?
Jim
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
|
|
|
| |
|
Home