I'm not sure what you mean here.. for each of the migration types, you can still call local_remote_migrate(). The only difference here is that the function will set up the VirtualSystemMigrationService object each time. Oops! I mixed two different things. Yes I had included the VirtualSystemMigrationService object creation to be able to use it for different migration types. Also, I was en quiring with you that if it is a good idea to include scenarios for all the migration types in one tc. Sorry for not being clear.
No problem! I think it's possible to include all the migration types in to one test. If it looks like the test will become too complex, then you can break it up. But I think it should be easy to add the others in without too much complexity. -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com